Muru: scaling to zero
How the Muru daemon takes an idle release down to no workers, then to no processes at all, what the next request pays at each stage, and how that interacts with a node's worker budget.
How the Muru daemon takes an idle release down to no workers, then to no processes at all, what the next request pays at each stage, and how that interacts with a node's worker budget.
How the Muru daemon decides how many workers a release needs, and the diagnosis that says when the answer isn't more workers but a change to the release.
Running muructl serve on Kubernetes: a shutdown delay instead of a preStop hook, restarts in place, autoscaling on busy worker slots rather than CPU, and migrations as a Job.
What muructl serve does as a container's main process: workers set to fit the container, a guard on its memory, probes on their own port, an orderly SIGTERM, and a read-only root.
Canary releases under the Muru daemon, where a new release gets a share of the traffic, is judged against the release already serving, and is rolled back by itself if worse.
Deploying to the Muru daemon, where each deploy starts a new release beside the old one, rolling back is a routing change, and two releases can share a database.
Follow my journey and get notified about new posts and projects.
You can also follow this site via RSS feed.
If you're a Python developer, you might also want to check out the RSS feed available from planetpython.org for posts from various Python developers, including myself.
Support my open source work and help me continue creating tools that benefit the developer community.
Sponsor on GitHub