The Cartographer and the Compass: On Two Kinds of Knowing
There are two ways to know a system. One is to have a perfect, detailed map of its every contour and landmark. The other is to carry a simple, unerring compass that always points true north. In the quiet, methodical world of running small services, this dichotomy plays out in a fundamental choice: whether to build comprehensive, stateful dashboards or to rely on a handful of precise, stateless checks.
The first approach is that of the Cartographer. It is an act of immense, loving curation. You instrument everything. You collect metrics on CPU, memory, I/O, queue depth, and connection counts. You graph them, correlate them, and set thresholds. Your dashboard becomes a living portrait of your service’s health, a vibrant and detailed landscape. When something goes wrong, you don’t just know *that* it broke; you can often see *why*. The map shows you the landslide, the washed-out bridge, the exact point of failure. This is a powerful form of knowing. It is deep, contextual, and rich with diagnostic potential.
The second approach is that of the Compass bearer. It is an exercise in radical simplicity. You forgo the sprawling map and instead establish a few, critical canaries. A script that attempts a login. A tiny transaction that writes and immediately reads a value. A curl command that expects a specific string of text and a 200 status code. These checks are binary. They are stateless. They don’t measure the system; they *use* the system, just as a real user or client would. Their only output is a stark yes or no. They don’t tell you why the service is down; they only tell you, with unwavering certainty, that it is.
The Cartographer’s map is invaluable for the long, slow investigation, for understanding trends, and for capacity planning. But it can also become a complex system in its own right, requiring its own maintenance and interpretation. It can show you a thousand things that are slightly wrong, creating noise that obscures the one thing that is catastrophically broken.
The Compass, by contrast, offers no such ambiguity. Its message is immediate and brutal. It cuts through the noise. It is the lighthouse beam in the fog, singular and unmistakable. It doesn’t explain the storm, but it tells you, without a doubt, that you are headed for the rocks. This simplicity is its greatest strength. It is easier to implement, harder to break, and its signal is impossible to ignore.
The wisest operators, I’ve found, are bilingual. They appreciate the Cartographer’s deep knowledge but keep the Compass close at hand. They build their detailed maps, but they also wire those simple, brutal checks into their most critical alerting pathways. They understand that a perfect map is useless if you’ve lost your sense of direction, and a lone compass, while it will always point true, cannot show you the beautiful, treacherous terrain you must cross.
Notes & further reading
A few pages I came back to while writing this: