Carving The Scheduler Out Of Our Orchestrator · Fly
fly.io · 4,222 words · saved by 1 readers
A deep dive into container scheduling and Flyd, our new orchestrator.
Author Name Thomas Ptacek @tqbf @tqbf Image by Annie Ruygt We’re Fly.io, a global sandwich-rating company with a hosting problem. Even if you don’t have a sandwich to rate, you might benefit from the hosting platform we built. Check it out: with a working Docker image, you can be up and running on Fly.io in just minutes. So, you want to build an app to rate sandwiches. Well, the world has a lot of different sandwiches. Pit beefs in Baltimore, Tonkatsu sandos in Shinjuku, and Cemitas in Puebla. You want real-time sandwich telemetry, no matter the longitude of the sandwich. So you need to run it
saved by
related reading
- k8s-1m Overviewbchess.github.io
- Kubernetestheswissbay.ch
- What we learned after running Airflow on Kubernetes for 2 years | by Alexandre Magno Lima Martins | Apache Airflow | Mediummedium.com
- Slurm Workload Manager - Wikipediaen.wikipedia.org
- We rebuilt the Kubernetes control loop on Postgres | Atlasflowatlasflow.com
- The feedback loops behind Kubernetes — PlanetScaleplanetscale.com
- Cluster Architecture | Kuberneteskubernetes.io
- Fly.io makes infrastructure easy for developers | by Pekka Enberg | Turso blog | Mediummedium.com
- The Design & Implementation of Sprites · The Fly Blogfly.io
- Thoughts on the Buildkite Aug 25 incidentsurfingcomplexity.blog
- Airflow Executors | Astronomer Documentationastronomer.io
- Paul Butler – The hater’s guide to Kubernetespaulbutler.org