True, but an ATM one thing, big transactions are different. And the high volume, highly available transactions are constrained to pools which are themselves handled with pessimism. You won't be able to walk away with a…
Differing views are a fact of life, but inconsistent views needn't be. But I think what you're asking is a question of how long a lag your app is willing to tolerate between Alice and Bob. Orly lets you set limits on…
Banking systems use limited availability rather than tolerate inconsistency. Banks are pessimistic.
In strict CAP terms, eventual concurrency is a form of limited availability, but it's a special enough case that I think it deserves separate consideration.
True, but an ATM one thing, big transactions are different. And the high volume, highly available transactions are constrained to pools which are themselves handled with pessimism. You won't be able to walk away with a…
Differing views are a fact of life, but inconsistent views needn't be. But I think what you're asking is a question of how long a lag your app is willing to tolerate between Alice and Bob. Orly lets you set limits on…
Banking systems use limited availability rather than tolerate inconsistency. Banks are pessimistic.
In strict CAP terms, eventual concurrency is a form of limited availability, but it's a special enough case that I think it deserves separate consideration.