The Humble Doorstop: On the Physics of Keeping the Door Open
It sits on the floor, a forgotten wedge of rubber or a kicked-aside block of wood. We use it without thought, jamming it under a door to let the breeze in or the sound out. The doorstop is the smallest, most unassuming member of our ops toolkit. It performs a single, vital function: it maintains a desired state. And like any good system, its reliability hinges on a beautiful, boring physics we take for granted.
Consider its operation. The doorstop doesn’t lock the door. It doesn’t command the door to stay open. It doesn’t even ask politely. It simply introduces a point of high friction and mechanical advantage into the system. When the door tries to swing shut, its force is translated by the wedge’s slope into a tremendous downward pressure against the floor. This pressure creates the friction that opposes the door’s motion. The system fails only when an external force—a strong gust of wind, a careless kick—overcomes this carefully balanced opposition.
This is not unlike a well-designed health check for a small service. The service doesn’t scream that it’s healthy; it simply exists, responding to a simple probe. The check doesn’t force the service to be up; it merely tests the conditions under which it would fail. The service is the door, held in its ‘open’ state. The health check is the doorstop, a small, constant verification that the forces keeping it there haven’t been overcome. It’s a passive guardian.
The Silent, Static Sentinel
There is a profound lesson in its simplicity. The doorstop has no moving parts. It has no battery to die, no software to patch, no configuration to drift. Its logic is etched into its shape. It is a monument to immutable infrastructure. You deploy it once, and it just *is*, performing its function perfectly until the environment around it changes so drastically that its simple rules no longer apply.
We chase complex solutions—automated scripts that restart services, elaborate load balancers that route traffic, intricate logging that alerts us to a threshold breach. These are necessary. But we should also cherish the doorstops in our systems: the static configuration file that never changes, the simple cron job that has run without error for years, the read-only user with just enough permission to perform one single, critical check. They are boring. They are reliable. They work not through complexity, but through a fundamental, unwavering understanding of the forces they are meant to oppose.
Next time you prop a door open, pause for a second. Look at that humble wedge. It is a quiet promise that some things, if built correctly, can just work. It asks for no credit, demands no attention. It just takes the pressure, and holds the line.
Notes & further reading
A few pages I came back to while writing this: