We rebuilt the Kubernetes control loop on Postgres | Atlasflow
How Atlasflow's control plane keeps your app in the state you declared, across regions, with a reconciler loop on Postgres instead of a cluster you have to operate.
We like Kubernetes. People here have run it in production at real scale, and a few have built and run managed Kubernetes that other companies deployed onto. So this is not the usual story of someone who bounced off kubectl and quit. It is the opposite. Everything we learned running it is why Atlasflow's control plane works the way it does. Here is what we learned. Kubernetes got one thing exactly right, and then wrapped it in a second full-time job. The thing it got right is the reconcile loop. The second job is running a cluster. We kept the loop, threw the cluster away, and run the whole con
Explore this link on the map →saved by
related reading
- The feedback loops behind Kubernetes — PlanetScaleplanetscale.com
- k8s-1m Overviewbchess.github.io
- Cluster Architecture | Kuberneteskubernetes.io
- Carving The Scheduler Out Of Our Orchestrator · The Fly Blogfly.io
- More Than DNS: The 14 hour AWS us-east-1 outage – Jonathon Belotti [thundergolfer]thundergolfer.com
- Kubernetes production readiness checklistlearnk8s.io
- What we learned after running Airflow on Kubernetes for 2 years | by Alexandre Magno Lima Martins | Apache Airflow | Mediummedium.com
- Paul Butler – The hater’s guide to Kubernetespaulbutler.org
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- Deploying R with kubernetes – Notes from a data witchblog.djnavarro.net
- Scaling App Infrastructure with Kubernetes & Microservicesrtinsights.com