We have ~2500 paying customers around the world. Getting rid of multi-tenancy would reduce the complexity a lot. I read:
And watched the talk on YouTube. However, Claude Fable tells me that I not only need to pay for the user’s data on the Fly volume, but also for the Docker image size for each fly machine?
As far as I understood a fly volume is not replicated anywhere? And that it is basically unavailable if the corresponding server of the fly machine is under maintenance? So I would need to use Litestream and restore the Sqlite db, if I do not have access to the volume anymore?
Would be great to have in-depth guide how you could realize such an architecture on Fly.
Those caveats are still valid on the Machines platform. The architecture described there is more for a limited niche of applications, either way.
Fly.io themselves probably intend people to use Sprites for this kind of thing now (or at least the near future). That solves the Litestream, etc., aspect that you mentioned, in particular, since backups to Tigris are built in to those at the filesystem layer. They just announced (a beta of (?)) an overhaul of the storage system, including the forking (“golden Sprite”) feature that you were asking about in your earlier thread:
[…] introduces two big subsystems that get us to a place I’d finally consider “feature-complete” for what we’re trying to do.
The first is the Sprite Block Device (SBD). The original Sprites storage stack was a goblin contraption I personally derived from JuiceFS and wired into our system using Ben Johnson’s Litestream. You should be glad to hear that Ben and Tim Newsham tore that whole stack down to the studs and rebuilt it. It’s faster, more reliable, and still does instant checkpoint-and-restore.
More importantly, SBD enables drive forking: you can create a template Sprite, and then efficiently clone millions of times.
[…]
Sprites are the right fit for our future customers, and a very large portion of our existing ones.
Hopefully that includes the ability to fork via the API, etc., …
(That, along with a minimalistic base image option, is the feature that I’ve most been waiting for, as well.)
@mayailurus thanks a lot for taking the time to answer. I also missed the lastest blog post about sprites thanks for sharing it. Yeah forking (“golden Sprite”) is really a missing part, hopefully the Sprite Block Device gets out of private beta soon.
…