3 ms·
I think CAP is really more about how much consistency and availablity you need. This FAQ talks about "relaxing" and that's the right word. Some systems tolerat
by shin_lao 11y ago
I think CAP is really more about how much consistency and availablity you need. This FAQ talks about "relaxing" and that's the right word.
Some systems tolerate that a database (for example) is unavailable for a couple of seconds. Some don't.
When you add a value into a distributed database, how much time are you ready to wait for replicas to propagate? In some cases it's fine to wait several minutes (think DNS) in some other it can have catastrophic results (think finance/banking use cases).
- pjc50 11y agoIronically finance has coped just fine with delayed-update replicas for centuries; that's what cheque clearing is. You issue a 'write' on a piece of paper, speculatively commit a transaction locally, but in the event of a write collision at head office it gets 'bounced' and the transaction rolled back.