Disaggregated Storage Is Becoming the Default Architecture
Two projects in today's threads, Walgit and Bookshelf, both use object storage as their primary persistence layer. Walgit is a Git server that is a single binary in front of an object store. Bookshelf is a self-hosted eBook library that runs on object storage. Neither treats local disk as the default.
A commenter in the Walgit thread made the key observation: Conditional Put shipped 21 months ago, and since then there has been a massive move toward disaggregated storage. The architectural shift is that object stores with compare-and-swap semantics are now good enough to build stateful systems on top of, without a separate coordination layer.
This is a concrete pattern, not a vibe. When hobby projects and Show HN submissions are defaulting to object storage as the obvious choice for persistence, that tells you something about where the infrastructure defaults have landed.
So what?
If you are designing a new service and reaching for a database as the default persistence layer, ask whether object storage with Conditional Put would work. For many read-heavy, write-occasionally workloads, it is cheaper, simpler to operate, and easier to scale. The Walgit approach of 'one binary plus S3' is a real architecture, not a toy.