Re:There's Just No Getting Around It: You're Building a Dist...
by saryant on Thursday April 27, 2017 @03:16PM
(#14213968)
I'm saying read replicas are not instantly in sync with their masters. Updates are asynchronously copied to the replica.
[ Parent
| on HN ]
Re:There's Just No Getting Around It: You're Building a Dist...
by peterwwillis on Thursday April 27, 2017 @04:49PM
(#14214571)
Or, you know, use synchronous replication, or semi-synchronous, or a different asynchronous model that isn't weakly consistent such as distributed transaction logs, write-read consensus, complicated locking mechanisms, etc
Re:There's Just No Getting Around It: You're Building a Dist...
by saryant on Thursday April 27, 2017 @04:59PM
(#14214654)
All of these solutions are still battling the fact that distributed systems are hard and there's a tradeoff to every decision.
If you use synchronous replication, you now require at least two systems to commit a write, so you've increased the chance that your commit will fail. Maybe that's the right choice—but it's a tradeoff and the decision ultimately rests in your business requirements.
My point is simply that there is no magic bullet in ensuring that all relevant systems have the same answer to the same question at the same time.