4 ms·
If I'm not mistaken, an eventually consistent database must also guarantee, well, eventual consistency.
by pron 13y ago
If I'm not mistaken, an eventually consistent database must also guarantee, well, eventual consistency.
- aredridel 13y agoSure! All nodes will be consistent in that your balance is what they all think it is, and that the attacker's balance reflects the attack. But unless those actions are coupled in a transaction, each account may not be consistent with the other.
- google-serf 13y agoThe problem is that while overdraft is very profitable for the bank; you acquire a legal liability to pay back that debt. Overdraft cannot be offered in a non fractional exchange and the exchange can't find you if you take more than your balance. Money leaving the exchange must be reconciled with holdings or they are insolvent. What we may see is blockchain denoted exchange holdings; your exchange wallet is unique and publically verifiable (only the exchange holds the keys). You could verify with balance with the address and all trades are performed on blockchain. Bitcoin would be inappropriate for this with its long confirm times but a newer faster scrypt or primecoin variant might do it. Exciting times!
- Alex3917 13y agoThe problem is that eventual consistency doesn't mean eventual correctness. The basic issue is that math usually only works if you do it in the correct order, e.g. (X+2)5 != (X5)+2. And if you're using a document store to do mathematical transactions then you're not guaranteed that they execute in the correct order, all that you're guaranteed is that all the nodes will eventually be the same in your database.
- nevi-me 13y agoBut debits and credits do not use multiplication nor division, so for those transactions the order doesn't matter.
- jamesaguilar 13y agoIf eventually consistent databases stored pending operations rather than pending values, this would matter. Unfortunately, they actually tend to be value based. So when you perform an operation on stale data, either the new operation will be lost, or the old one, depending on the implementation.