7 ms·
It depends on the application. For Netflix, transient glitches like having outdated play history or catalog entries that take a while to propagate aren't hugely
by Scaevolus 12y ago
It depends on the application. For Netflix, transient glitches like having outdated play history or catalog entries that take a while to propagate aren't hugely detrimental -- the core value of serving the videos that users request doesn't depend at all on having a consistent view of quickly-changing user data.
For more complex applications (think Facebook), there are useful consistency models other than strong consistency, with causal consistency being one of the most promising: http://queue.acm.org/detail.cfm?id=2610533 http://queue.acm.org/detail.cfm?id=2610533
- cordite 12y agoIf they are often watching full episodes or movies, I wouldn't call it very quick. Though progress state would be changing near constantly.
- _delirium 12y agoDo you know whether the linked article is what Facebook is currently using, or a proposal? Facebook is an example of a webapp that fairly often has user-visible weird behavior, like "read" notifications becoming unread again. But I'm not sure if those are glitches, or a result of their consistency model.
- MoOmer 12y agoFacebook wrote Cassandra for such scenarios. https://m.facebook.com/note.php?note_id=24413138919 https://m.facebook.com/note.php?note_id=24413138919