4 ms·
Offtopic, but I find it funny how we use banks as the paramount example of a need for consistency, when they're actually not :)
by icebraining 10y ago
Offtopic, but I find it funny how we use banks as the paramount example of a need for consistency, when they're actually not :)
- rantanplan 10y agoI would be interested if you could elaborate a bit.
- chillax 10y agoperhaps refering to this? http://highscalability.com/blog/2013/5/1/myth-eric-brewer-on-why-banks-are-base-not-acid-availability.html http://highscalability.com/blog/2013/5/1/myth-eric-brewer-on...
- DrJokepu 10y agoBanks basically don't use database transactions to record financial transactions. Instead, failed operations are rolled back with an inverse operation. It's done this way to ensure that there is an audit trail of every operation, rolled back or not.
- djsumdog 10y agoHuh. So banks really couldn't use event sourcing could they? Oh maybe they could so long as every failure was a new event.
- tmd83 10y agoI would assume that banks can be the best enterprise profile user of event sourcing. For traditional application we use the DB rollback for failure mitigation and banks are actually explicitly doing that. I think the event is already there and they are essentially using the same concept as event sourcing if I'm not mistaken. And I think its much easier to make it work. There is a lot of associated domain and logic but the core of banks is a series of transactions (never worked so could be completely wrong) .. source, destination, amount. It looks poster child for event sourcing/log based architecture.
- inopinatus 10y agoI have worked in FSIs and the DBAs I met were absolutely paranoid about consistency and durability of writes to core banking databases. Curiously it was atomicity and isolation that took a back seat, errors due to those would be corrected by applications (or by hand in exception processing) with reversing transactions.