HN Reader

I found myself thinking about Cloudflare Durable objects new SQLite offering.

Nicely detailed here https://simonwillison.net/2024/Oct/13/zero-latency-sqlite-st... And https://developers.cloudflare.com/durable-objects/best-pract...

Whenever I saw the claim that “S3 is cheap “, I just cannot take it too seriously.

There is also SlateDB, another work in progress take on this. HN link: https://news.ycombinator.com/item?id=41714858

TiDB Serverless is built on S3, it's in production for more than 2 years, Blog link: https://me.0xffff.me/dbaas2.html

Pretty cool! Do you have any ideas already about how to make it work with S3, considering it doesn't support If- headers?

I appreciate the effective use of diagrams. The boundaries are separated really nicely.

Pretty cool and could be useful for stuff that isnt updated so frequently like a CMS.

If I had time, I'd like to implement an Iceberg catalog this way.

Was it considered to separate each table into its own S3 object?

Congrats on reinventing the data lake? This is actually how most of the newer generations of "cloud native" databases work, where they separate compute and storage. The key is that they have a more sophisticated caching layer so that the latency cost of a query can be amortized across requests.

so... Delta Lake?