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
ksajadi 2 hours ago [-]
looks very similar to markbase.cloud
the_alchemist 4 hours ago [-]
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?
drifkin 3 hours ago [-]
the compare-and-swap prevents out-of-sync instances from stomping on the source of truth manifest
see: https://news.ycombinator.com/item?id=48661938
[0]: slivingdoc.dev
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.
And it has since Terraform v1.11