3 ms·
Good points, but it doesn't mention the reason I think that Fly (and Cloudflare) are doing server-side SQLite in the first place, which is to have a db "at the
by anentropic 2y ago
Good points, but it doesn't mention the reason I think that Fly (and Cloudflare) are doing server-side SQLite in the first place, which is to have a db "at the edge" to go with their edge compute model
Whether that's necessary or useful for your use case is another question
- tracker1 2y agoAlso with mentioning Turso's efforts in a similar vein. Definitely interesting conceptually. But I question if something like cockroach could be just as good in practice.
- anentropic 2y agoI think the point of "edge db" is mostly to reduce latency Otherwise the point of the article stands - using a conventional db server solves all the bits that are difficult with sqlite as a backend
- WorldMaker 2y agoAlso "at the edge" sometimes often implies read-heavy applications and places where you can bake essentially "static" DBs. In theory all the SQL query power benefits of a full RDBMS, but with the presumed simplicity of (mostly) static file deployments via traditional CDN file copies. Many applications are going to be write-heavier than that. Many applications don't need to distribute database deployment by "simple file copying" to potentially hundreds of "edges". But there are certainly interesting use cases for that when you can be read-heavy, deal with write trade-offs, and can easily "simple file copy everywhere" a DB. (Though I think most of the ones I find interesting are more Datasette and its plugins than Fly/Cloudflare style.)