3 ms·
> I think its pretty unlikely (in terms of db design) that you'd have a consistent system that could service reads but not writes during some manner of outage.
by vidarh 9y ago
> I think its pretty unlikely (in terms of db design) that you'd have a consistent system that could service reads but not writes during some manner of outage.
Consider a bank account. I can consistently service writes that add or subtract from the balance as long as I can guarantee durability and is willing to blindly update without a consistent view of the balance.
I can only service consistent reads when I can guarantee that I have seen every committed transaction.
In this case we opt for availability over consistency when presenting the current balance, but for consistency when e.g. cutting statements (through the brute-force method of just waiting until all settlement for the relevant dates has occurred).
- jacobparker 9y agoI think you misread my comment; I said its unlikely to have a consistent system that can service reads but not writes during some manner of disruption.
- vidarh 9y agoAh, yes, I read it as exactly the opposite in fact. But there are lots of consistent systems that can service reads but not writes during disruption. Databases with synchronous replication, for example would typically continue to handle reads, but fail writes, during a partition.
- jacobparker 9y agoTrue, good point!