Tbh, Dhaka traffic is a distributed system.

"How does anyone get anywhere these days?"

He says it the way a man says it after he has already said it twice and isn't sure whether he is asking a question or filing a complaint with the universe. The wiper that still works clicks once on the dry glass and stops. A CNG to the left honks twice in the slow two tap that means the driver is about to do something stupid, and a moment later he does it.

Fariduddin watches the manoeuvre finish without a scratch.

"It works because nobody is in charge," he says. "I know how that sounds."

Robert looks at the windshield like it owes him an apology. Fariduddin reaches for the lukewarm cha in the cupholder. He has been waiting forty minutes to explain a thing he has been thinking about for fifteen years.

What outsiders hear as noise is a gossip protocol with at least three message types. The slow two tap announces "I'm about to do something stupid," broadcast before the manoeuvre. The rapid staccato is the reply, "you're doing something stupid, please stop," sent by anyone close enough to be inconvenienced. The long unbroken lean translates to "yield or die, I have committed," and acknowledgement is implicit, because if nobody slams a brake then consensus has been reached.

Robert tilts his head. He has heard the slow two tap three times in the last minute and not noticed it as language until now.

Right of way at this intersection is local consensus, not law. The cars and CNGs and rickshaws and the occasional pedestrian on a phone call are running a small Paxos round, and whoever proposes most credibly wins. Credibility is bumper paint plus vehicle mass plus eye contact, and the decision binds only the four or five nodes who happen to be standing in it. The chowrasta two blocks down doesn't need to agree on anything, which is the entire trick.

Leslie Lamport wrote this up in 1978 in Time, Clocks, and the Ordering of Events in a Distributed System. You don't need a global clock. You need a partial ordering and a way to break ties. The tiebreaker on Mohakhali Road is the long honk.

"You see him? That one, the rickshaw on the left?"

The rickshaw puller is a background process that does not respond to SIGTERM. Traffic moves around him, the warden waves at him, the car behind honks the rapid staccato. He continues at the speed of a man who has been pedalling since before dawn and has correctly concluded that none of you will physically remove him from the road. He is right about that. Every distributed system has a process like this one, and you route around it rather than try to kill it.

Robert watches the rickshaw thread a gap that a polite driver would have called impossible. He starts laughing the way you laugh when you realise the joke has been on you for a while.

The CNG driver is a stateful worker with a private fee schedule. The meter on the dashboard is decorative, and the actual price gets computed through a handshake that takes three steps, weighing destination, weather, and how desperate you look while standing at the side of the road waving. You will pay more than the meter would have priced, and that markup is how the system has priced in the deception. The fare gets quoted, you counter, he refuses, you walk three steps, he calls you back, and somewhere between the third and the fourth round you have agreed on a number.

Then there is the warden. He arrives around eight in the morning at the Mirpur Road circle, performs leader election by sheer presence, and runs the show for ninety minutes. Then the heat hits, the vest goes back into the booth, and the system loses its leader. For three or four minutes everything is worse, and a Pathao rider yells something unprintable at a Noah van. After that, local consensus takes over and throughput recovers, which is what every Raft cluster does when the leader dies, just on a more humid schedule.

"This is the part where somebody dies, isn't it?"

Classic deadlock shows up most evenings at Banani 11, where four streams meet and each refuses to yield, every node waiting on a resource held by another node, until nothing moves at all for ninety seconds. The only resolution is an external process, usually a man in a fluorescent vest pulling one vehicle out of the wait graph by the bumper. All four Coffman conditions, satisfied on a Tuesday at half past five, witnessed by anyone who has ever cut through Banani after work.

Network partition is what a hartal looks like from inside the system. Streets close, zones become unreachable, riders inside one partition can still talk to each other but not to the other side, and each partition stays up with stale state until things heal. When the barricades come down in the evening, the two halves merge noisily, with rumours about what happened on the other side and a half hour of lane discipline being even worse than usual, eventually consistent, the way Dynamo says it should be.

So we route around them, with a lot of horn.

"I'm not making a tourism argument, by the way. I'm making a software one."

We have spent fifteen years assuming good systems need strong coordination, a central database, a single source of truth, a leader, and we pay for it in latency and in the misery of keeping the coordinator alive. Dhaka, running every weekday between Tejgaon and Gulshan, is the proof that local-first protocols can beat global coordination at the scales that matter to most of us. You don't need every car to know every other car's position. Each car needs to know about the four around it and honk competently, and throughput emerges from there.

A polite car yields earlier than necessary and pays a small individual cost so the system pays a smaller global one. That is genuinely a kindness. It is also why the system in Berlin breaks the moment somebody fails to be kind on schedule. Dhaka skips the politeness layer and pays the cost directly with a horn and a forearm out the window, which is uglier and noisier and, on the dimensions Lamport was actually writing about in 1978, demonstrably more resilient. The map of who spoke to whom is the system you are actually running, not the clock on the wall, which was decorative the whole time.

Build software that needs every node to agree on the time before anything moves, and you have built Dortmund, which is lovely and slow and falls over the moment one node stops answering. Build software where each node knows about the four neighbours nearest to it, gossips with them competently, tolerates the occasional Aricha truck convoy that won't read the spec, and keeps moving when the leader goes home at noon, and you have built something that looks like the Mohakhali junction at half past five on a Tuesday in February. That junction is the system I would rather be running on a bad day.

The light at the chowrasta turns green. The CNG to the left has already started moving on the slow two tap, two seconds before the light, because his protocol stack reads the cars in front of him and not the bulb on the pole. Robert watches it happen and laughs again, quieter this time, and Fariduddin pulls out into the gap behind the CNG without waiting for anyone to tell him it is his turn.