· Architecture · 6 min read
Leaving Docker Compose without adopting a cluster
By Ethan Cole, Co-Founder & CTO
Compose is a great way to run a laptop. It is a thin way to run production. Here is the gap teams actually hit.
Compose deserves its reputation. A short file, a local network, and a new teammate can boot the stack before lunch. Keep it for that.
The trouble starts when the same file becomes production. Restarts are coarse. Secrets live in a dotenv someone copied. Staging is a second host with a second file that drifted in March. Scaling one service means a shell loop. When the web process dies at 2 a.m., the alert is a customer.
The usual next step is Kubernetes, and the usual next six months are not the product. You wanted a health check and a second environment. You got a control plane to operate.
The gap is specific. You need isolated environments, startup order, a rollout that stops if the probe fails, secrets that are not in git, and a way to scale the one service that is actually busy. You do not need to design a cluster to get those.
That is the move Nimbus is for. Bring the images you already build. Describe the dependencies you already know. Leave Compose on the laptops, where it is good.