I <i>highly</i> recommend anyone using this to use a Durable Object <a href="https://developers.cloudflare.com/durable-objects/" rel="nofollow noreferrer">https://developers.cloudflare.com/durable-objects/</a> for writes as this project doesn't seem to have consistency guarantees. If the Worker that writes to a collection happens to both do a write at the same time the data will be whatever the last Worker to write set it to.<p>Very cool library for read-centric use cases but I'd be very careful using this for use cases with frequent writes.
Slightly OT but I found the experience of maintaining and deploying workers to be terrible and so monorepo-unfriendly due to wrangler forced usage for deploys (or at least I haven't found better ways) which has implications on how the project gets bundled and deployed.<p>I wish there was a simple stupid "just drop an artifact with a main.js" file and that's it.<p>Cloudflare is one of those companies I really want to like, but as a developer I just don't think they care. They want to chase big guys with big contracts that can get the love and support average Joe does not.<p>They seem to strongly underestimate the traction and money they could get by giving engineers rather than sales and accounts some more love.<p>And thus we have moved our stack, initially built around Cloudflare, to Azure. It also helps Microsoft throws lots of credits at startups and Cloudflare does not. But DX rather than money has been the biggest reason we moved off CF offerings.
interesting. I can see how this differs from D1 and kv store, but what usecase for doing it this way? was there something kv store and D1 was not enough for?