انتقل إلى المحتوى
#0716
DaemonCronContainers

Retire the orchestrator

Your docker-compose.yml lists a web server, a worker, a queue, and a nightly job. Somewhere, a compose daemon or a Kubernetes control plane exists to keep that true.

Move the stack into one container. Each service registers as a daemon program; the boot order is a priority number on each one; the nightly job is a cron line. Crash recovery is autorestart on the program that crashed. Every one of those is a POST you can make from anywhere, including a phone.

The orchestrator was a piece of software you ran so that other software would run. Here the supervision, the scheduling, and the restart policy are properties of the container itself, managed over HTTP.

Nothing is in charge of the stack, and the stack comes up anyway.