4 ms·
If you threw strong consistency out the window and kept low latency you're still getting the "make profile private" event well before the user has navigated to
by RhodesianHunter 5y ago
If you threw strong consistency out the window and kept low latency you're still getting the "make profile private" event well before the user has navigated to the post page and composed a tweet.
- deleted 5y ago[deleted]
- saryant 5y agoThe 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.
- Bjartr 5y ago"and kept low latency" is not a reasonable assumption in the face of real world networks.
- NavinF 5y agoIf the latency is bounded, then you have strong consistency. Just add a sleep(5) call after every write to make it linearizable.
- ignoramous 5y agoWhat if the process interrupts before it could sleep(5) and restarts...
- NavinF 5y agoStill 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.
- lubesGordi 5y agoLatency is never bounded, in fact that is what the P is in CAP.
- NavinF 5y agoYep. It was not a serious suggestion. Without partitions, everything would be easy so it’s kinda silly to assume low latency.