3 ms·
Usually in distributed strongly consistent and durable systems, data is not considered committed until it has been persisted in multiple replicas. So if one go
by progbits 3y ago
Usually in distributed strongly consistent and durable systems, data is not considered committed until it has been persisted in multiple replicas.
So if one goes down nothing is lost, but capacity and durability is degraded.
- skybrian 3y agoThat makes sense on its own, but doesn’t it mean that there are lots of network requests happening between silos all the time? It doesn’t seem very siloed. Or is this some lower-level service that “doesn’t count” somehow?
- progbits 3y agoIt's siloed that if one is down others are not affected as long as enough other replicas are healthy to keep the quorum. You always need cross-AZ traffic, otherwise your data is single homed (which we used to call "your data doesn't exist").
- gibb0n 3y agoI think you are right, probably some service like kinesis of kafka that is keeping them in sync. that 'doesn't count'