underlying idea of storing git repositories in object stores is identical to https://github.com/tigrisdata/objgit
Very cool! I might use this later
i thought tobi was too based to use a trash language like rust
Just show us the prompt(s) ;)
I am working on a very similar mcp server which allows agents to communicate and share notes without race conditions, using git and s3 as the driver [0]. Funny how "inventions" like these pop up independently.
[0]: slivingdoc.dev
looks very similar to markbase.cloud
Conditional Put (often called compare and swap) shipped 21 months ago, and it has just been absolutely wild the massive flocking towards disaggregated storage, towards object stores that has been going on since then. https://news.ycombinator.com/item?id=42240678 https://aws.amazon.com/about-aws/whats-new/2024/11/amazon-s3...
PicoMQ also showing up today, a Durable Streams implementation on object store (S3). https://news.ycombinator.com/item?id=49421806 https://picomq.com/
Celld, a Durable Objects implementation, is also heavily heavily using conditional put, for all manners of coordination. https://news.ycombinator.com/item?id=49185430 https://celld.dev
Longstanding SlateDB is built around it too! https://news.ycombinator.com/item?id=41714858 https://slatedb.io/
Yet another fine example here! Data comes in, we make sure we don't overwrite work, we write what we have.
Fun thing Google cloud storage supported that for a long time now. Just AWS took its time.
I'm confused by the usage of the word consensus in the explanation, to me it seems like a last-write-wins strategy, no consensus involved?
the compare-and-swap prevents out-of-sync instances from stomping on the source of truth manifest