Carving the Scheduler Out of Our Orchestrator
Blog post from Fly.io
Fly.io is a global sandwich-rating company with a hosting problem. They built a platform using Docker images and an orchestrator called flyd, which operates like a market where requests to schedule jobs are bids for resources. The system has three main components: flyd, flaps, and flyctl. Flyd is the source of truth for all VMs running on a particular worker, while flaps acts as a broker between users and flyd instances. Flyctl, their CLI, takes over complex policy-heavy functionality in the platform. The new design, called "AppsV2", exposes basic primitives directly and allows them to write code to configure it the way they want.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Kubernetes | 18 | 1,426 | 152 | 70 | -1% |
| Real-time | 1 | 1,631 | 434 | 158 | -10% |
| Serverless | 1 | 530 | 128 | 70 | +21% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.