Hacker News Reader

"and kept low latency" is not a reasonable assumption in the face of real world networks.

The problem is ensuring that event has been propagated all around the world so you aren’t displaying now-private tweets. That’s why we need strong consistency.

I have spent much of my time at this company on this exact problem.

If the latency is bounded, then you have strong consistency. Just add a sleep(5) call after every write to make it linearizable.

What if the process interrupts before it could sleep(5) and restarts...

Still linearizable under the insane assumption that the db is always “low latency” which implies it never goes down. The write either happened or it didn’t.

Latency is never bounded, in fact that is what the P is in CAP.

Yep. It was not a serious suggestion. Without partitions, everything would be easy so it’s kinda silly to assume low latency.