This looks interesting for read heavy distributed apps. I.E fly.io/aws lambdas/k8s. Each instance gets its own eventually consistent read only copy of the db.

This looks interesting for read heavy distributed apps. I.E fly.io/aws lambdas/k8s. Each instance gets its own eventually consistent read only copy of the db. So instead of making a network request to go get some data, you query your local cache. Your use case is that you are read heavy for this to fit your needs. If you have a copy of the data local to you, you don’t need to go bug another team to expose it via an API. Reading fly’s blogposts it’d be good to see more on write durability. They’re batched on the client, batched on fly’s side before being compacted to s3 from reading so you can loose writes before your client as sent them to fly, possibly loose them before fly has written to s3 depending on how they implemented. FlyCloud might make a great service for small typical Wordpress type sites or low user services where writes are low. It’s a shame they don’t offer pay as you go for the LiteFS product only. I get why they don’t as they want you to host with them but it’d be great if you could pay as you go on the db only. I currently use DynamoDB for low volume stuff for cost reasons, it costs me cents. Productivity is extremely low though with Dynamo as you need to think very hard about table design and constraints and work around those constraints. It’s a lot more effort than using something like SQLLite for quick simple stuff.