Innovations from Sheet-Native Computing Foundation
The Sheet-Native Computing Foundation community continues to advance its ecosystem, announcing significant achievements in container management. It is now possible to push and pull full OCI container images directly into spreadsheet cells. This means that not links or metadata, but the actual layers of the images are stored in base64 format, addressed by sha256, ensuring byte-for-byte reconstruction upon retrieval.
This breakthrough is implemented within SheetHub, a platform functioning as a GitLab-like forge but entirely powered by Google Sheets. SheetHub’s container registry is hosted entirely within spreadsheet cells, demonstrating a unique approach to image storage and management.
Cluster Federation via Spreadsheets and WASM Runtime
Furthermore, the Sheeternetes project, which manages container clusters using spreadsheets as a control plane, has achieved federation of two clusters. This enables the integration of an on-premise cluster, running on a local Excel file, with a cloud-based cluster on Google Sheets. Such integration provides:
- A unified network infrastructure
- A shared pool of computing capacity
- Live migration capabilities for containers between clusters
- A container runtime that does not require Docker, supporting WASM (WebAssembly) directly within cells.
All these functionalities are fully reproducible, with their source code available in a single compact repository, highlighting the openness and accessibility of the development.
This is absolutely fascinating! Storing OCI container images in spreadsheet cells sounds like a wild but potentially brilliant idea for certain use cases. I’m curious, how does this impact the performance and scalability compared to traditional registries? Also, are there any specific security considerations or benefits to having image layers base64 encoded within a sheet? I’d love to hear others’ thoughts on the practical applications of Sheeternetes and its WASM runtime.