The Switchboard and the Single Point of Truth
Before we had distributed systems, we had switchboards. Before we had service discovery, we had operators. And long before we worried about a single source of truth for our application state, a massive network ran on the principle that there could only ever be one. I’ve been thinking lately about the old Number Five Crossbar switching systems and the women who made them work, because they understood something about state and consistency that we often struggle with today.
These electro-mechanical behemoths were the backbone of telephony for decades. Their core logic was deceptively simple: a call’s path was physically established by relays and switches, a literal circuit created through the machine. The entire state of a connection—who was calling, who was being called, whether the line was busy or ringing—was not stored in some ephemeral cache or a distributed database. It was represented in real-time by the tangible, physical position of thousands of tiny metal components. The system’s state was the machine itself.
The Operator's Watchful Eye
But the hardware was only half the story. The system’s human operators were its living, breathing monitoring service. When a switch became stuck or a relay failed to engage, the machine would fall silent. The constant, familiar hum of successful connections would cease. This silence was the ultimate alert. An operator would then rise, locate the silent panel among a vast room of noisy ones, and gently tap the switch with her finger. This small physical intervention—a nudge to a stubborn piece of state—was often all that was needed to clear the fault and restore the machine’s song.
There was no A/B testing, no blue-green deployment, and no need for consensus algorithms. The state was absolute and authoritative because it could only exist in one place, in one form. You could look at it, touch it, and hear it. If there was a disagreement between what the subscriber experienced and what the machine displayed, the machine was never wrong. Its physical reality was the final word.
We now build systems of incredible complexity and abstraction, where state is copied, sharded, and eventually consistent across continents. We gain flexibility and scale, but we lose the elegant, brutal simplicity of a single, authoritative source of truth. We trade the operator’s intuitive ear for a deluge of aggregated metrics and log alerts, hoping our dashboards can approximate her innate understanding of the system’s healthy hum. The lesson from the crossbar switch isn’t that we should return to electro-mechanical relays. It’s a reminder to design our digital systems with the same clarity of state. To know, with certainty, where the truth resides, and to build services so simple and reliable that their failure announces itself not with a screaming siren, but with a profound and telling silence.
Notes & further reading
A few pages I came back to while writing this: