A wall-clock label such as 2026-11-01 01:30 does not identify one instant by itself. Its interpretation depends on a timezone and sometimes on which occurrence was intended during a clock transition. Conversely, an explicitly defined Unix timestamp already carries epoch and unit semantics without displaying a zone name. Decide which kind of value your system is storing before choosing a format. ...
sysctl is not a configuration file format. It is a live view of the kernel’s parameter table, reachable by dotted name and mirrored under /proc/sys, so reading and writing a value is literally reading and writing a pseudo-file. That is why sysctl -w takes effect immediately and why nothing set that way survives a reboot. ...
Logrotate evaluates configuration when invoked, rotates eligible logs, and applies the selected retention and compression actions. A timer or another scheduler determines when that evaluation happens. The tool does not continuously cap file size, and renaming a log does not automatically redirect an application’s open descriptor. A working setup combines evaluation frequency, file policy, and the writer’s actual reopening behavior. ...
cgroup v2 organizes resource control in a unified hierarchy. A workload’s processes can share aggregate budgets, with limits inherited through the hierarchy rather than applied only to one particular PID. CPU bandwidth, memory usage, and task count are separate controllers with different enforcement behavior. Reading the actual cgroup files and failure counters is more useful than treating every configured limit as the same kind of hard stop. ...
A reverse proxy accepts client requests and makes a separate upstream exchange with an application. It can centralize routing, transport, headers, and admission policy when those behaviors are configured. It does not automatically hide every backend interface, authenticate every caller, or terminate TLS. The useful boundary is the actual traffic path and policy applied there, not simply the proxy’s position in a diagram. ...
A migration that rewrites a busy table in one committing statement is long and blocking. A sequence of small, backward-compatible changes moves the same schema forward with no maintenance window, because each step is separately deployable and separately reversible. What is being managed is a lock, and the question is how long it is held — which depends on how much data the statement touches. ...
Two full environments for the same service, both able to serve, with a router deciding which one receives traffic. The new version is deployed to the idle colour and runs the entire pipeline — provision, migrate, deploy, smoke test — while the live colour keeps serving. When the tests pass, the release happens as a routing change. ...
Deploys are where engineering risk meets production. A change flipped to 100% at once converts any mistake into an all-or-nothing incident. A rollout by phases turns the same change into a series of small, reversible measurements. Equal percentage is not real safety Reaching a 100% cutover in one step is not speed, it is a bet that you can read a log before the whole fleet dies. Percentage as a number is meaningless on its own, because 50% of traffic to a service you broke is still a full incident. What a progressive rollout actually buys is reversibility: the ability to stop and pull back while most users are still on the old version, so a bad change at 5% is discovered and reverted while 95% of users never felt it. That property, not the arithmetic of the percentage, is the point. ...