The Design & Implementation of Sprites · The Fly Blog
fly.io · 2,301 words · saved by 1 readers
So that we may educate as well as horrify: the internals of our new Sprites execution platform.
Author Name Thomas Ptacek @tqbf @tqbf Image by Annie Ruygt We’re Fly.io, and this is the place in the post where we’d normally tell you that our job is to take your containers and run them on our own hardware all around the world. But last week, we launched Sprites , and they don’t work that way at all. Sprites are something new: Docker without Docker without Docker. This post is about how they work. Replacement-level homeowners buy boxes of pens and stick them in "the pen drawer". What the elites know: you have to think adversarially about pens. "The purpose of a system is what it does"; a ho
saved by
related reading
- Kubernetestheswissbay.ch
- Building and operating a pretty big storage system called S3 | All Things Distributedallthingsdistributed.com
- NYSRGnotes.ekzhang.com
- How to Rack 30 Petabytes of Storage | blogsi.inc
- Fly.io makes infrastructure easy for developers | by Pekka Enberg | Turso blog | Mediummedium.com
- Git at any scalecursor.com
- Carving The Scheduler Out Of Our Orchestrator · The Fly Blogfly.io
- Code Storage by the Pierre Computer Companycode.storage
- Spritelyspritelyproject.org
- Together AI | The AI Native Cloudtogether.ai
- Our Stack · Fly Docsfly.io
- The subtle beauty of Durable Objects, and what could be better about them / Moment devlogmoment.dev