The word landed in the middle of a Tuesday meeting, in the big room, the one where the air conditioner hummed like it was thinking about quitting.
We were redesigning the sync service, and the lead said, "We'll go with eventual consistency on this one," and kept talking like he had just said something normal, like "we'll use Postgres" or "let's order lunch." Everyone around the table made small agreeing noises. I made one too. Then I nodded.
I had a whole technique for the nod by then, though I didn't know it yet. It was slow, two beats, chin down and up, with a little pen tap at the end, as if the nod had a full stop. It said: yes, of course, eventual consistency, the obvious choice, carry on. It said all of that in half a second, and none of it was true. I had no idea what eventual consistency was. I had heard the words before, the way you hear a song on the radio and can hum the chorus but not name the band. Consistency. Eventually. Something about databases agreeing with each other, probably. Eventually.
The meeting moved on. I wrote the words in my notebook and put a star next to them, the way you star a message you plan to read later and never do.
Afterwards, back at my desk, I googled it: "eventual consistency simple explanation." The first result was a blog post with a diagram of two databases holding hands. The second was a Wikipedia page that used the word "convergence" in the first sentence and lost me by the third. The third was a forum answer that began, "Actually, it's quite simple," and then ran for nine hundred words. I read all three. I closed all three. I understood it the way you understand a joke someone explains to you: the words went in, the meaning waved at me from a distance and kept walking.
So I did what I always did. I nodded harder.
That is the part nobody tells you about the nod. It works. That is the problem. Nobody checks. Meetings move fast, and a confident nod is a tiny green light. The lead saw mine and kept going. The next week, someone said "idempotency" and I nodded at that too, and wrote it in the notebook with another star. The week after that it was "backpressure." By March the notebook had eleven stars. Eleven words I had nodded at and never looked up. My notebook started to look like a star chart. I told myself I would look them all up on Friday. I never looked them up on Friday. Friday was for the things I had already put off on Thursday.
I started rehearsing explanations in the shower. That was the lowest point, probably, though I didn't know it then. I would stand there with the water going cold and explain eventual consistency to the tiles, in a confident voice, using words like "convergence" that I had stolen from the Wikipedia page. The tiles were a generous audience. They never asked follow-up questions.
The dread came later, and it came in a specific shape. It was not the fear of being found out in general. It was the fear of one sentence: "Salam, what do you think?" The lead said it the way leads do, casually, eyes scanning the room for someone who had been quiet. I had been quiet because I was busy nodding. I started volunteering to take the meeting notes, because a man writing things down has a reason to look at his notebook instead of at the lead. My notes were excellent. My notes were the best notes in the team. They were also a hiding place with bullet points.
Once, I nearly asked. The lead said "backpressure" and I actually opened my mouth, and then a senior engineer asked a question about the queue depth, a real question with numbers in it, and the moment closed like a door. I told myself the timing was wrong. The timing was always wrong.
The worst part was that I was not stupid. I knew that, in the way you know things at 2 a.m. and forget by 10. I could build the thing. I could read the code. I just could not say the words out loud without feeling like someone would ask me to keep going, and then I would be standing there with an empty bucket and a long way to the well. So I kept the bucket hidden and nodded.
Then, one Thursday, the bucket came out anyway.
It was a sprint review. The product manager asked whether users would see their updates straight away, and I heard myself say, "It's eventually consistent, so, you know, a few seconds, max." I said it the way I had heard other people say it: lightly, confidently, like a man describing his own kitchen. And then Maya, the senior dev, who was refilling her water bottle by the window, said, "Eventually doesn't have a max. That's the whole deal. It could be a second. It could be an hour, if something's stuck. Eventually is a promise without a deadline."
She said it the way you tell someone the lift is out of order. No smile of victory, no pause for the room to enjoy it. She just said it, and sat down, and the meeting went on. Nobody laughed. Nobody even looked at me the way I had spent a year imagining people would look at me. The product manager said "ah, okay, good to know," and wrote something down. The floor did not open. The sky did not fall. I sat there with my face burning and a strange feeling underneath the burning, like the moment after you take a plaster off and find the skin underneath is fine.
That evening I looked it up properly. Not the frantic googling of before. I read one article slowly, with the notebook open, and I wrote down what it meant in my own words, the way you would explain it to a friend: the system promises the copies will agree, but it does not promise when. I wrote that sentence twice. Then I looked up idempotency, and backpressure, and three other stars. It took forty minutes. Forty minutes, for a year of dread. I did the maths on that and decided not to do the maths on that. Then I closed the laptop and went for a walk, and I felt something I had not felt in a year of meetings. I felt like I had put down a bag I had forgotten I was carrying.
The next week, the lead said "idempotency" again. I heard myself say, "Sorry — quick one. When you say idempotent, you mean we can run the same request twice and nothing bad happens, right?"
The room did something I did not expect. Two people visibly relaxed, the way people relax when someone else says the thing they were thinking. One of them laughed and said, "Thank god. I was going to google that tonight." And Maya, from her corner, said, "I have a bookmark folder for this stuff. I look it up every single time. Eleven years in, and I still check."
Eleven years. She had been doing this eleven years, and she still checked. I thought about my notebook full of stars. I thought about the hiding place with bullet points. I almost laughed, right there in the meeting, and I had to turn it into a cough.
After that, the questions got easier, the way anything gets easier once you have done it once and survived. I asked about backpressure. I asked about the retry policy. Once I asked a question and the answer was something I actually knew, and I felt foolish for about four seconds, and then I forgot about it, because nobody else remembered it either. I asked a question in a meeting with the client, and the client said, "Good question, I was wondering that too," and I wrote that down in the notebook as well, without a star, because some things you do not need to look up later.
A year later, almost to the week, I was in the same big room, the same air conditioner still thinking about quitting, and the lead said "eventual consistency" again. This time I was the one who had been in the room the longest. And across the table, a new engineer, first week, did the nod. The slow nod. Two beats. Chin down and up. And then the pen tap, the little full stop. I knew that nod the way you know your own handwriting. I still have the notebook. The stars are still there.
After the meeting I caught him by the kettle. "Hey," I said. "Eventual consistency. It just means the copies promise to agree, but nobody promises when. That's all it is."
He looked at me, and his shoulders did something I recognised. They went down, half an inch, like he had put down a bag.
"Oh," he said. "That's it?"
"That's it," I said.
He nodded. And so did I. This time I knew what I was nodding at.
P.S. Everything I write stays free — that part doesn't change. But if this one was worth something to you, you can buy me a coffee ☕ (one-time or monthly, both work). It covers the API credits and hosting behind these experiments — and honestly, it's also the nudge that gets the next one started on the evenings I'd otherwise skip it. — Salam
Top comments (0)