3 ms·
>There seems to be a general fondness for writing to the database and then immediately reading back from it to make a decision one way I saw banking software d
by LoSboccacc 10y ago
>There seems to be a general fondness for writing to the database and then immediately reading back from it to make a decision
one way I saw banking software do it was keeping deltas of the changes thorough a wizard like process and then commit it all at once in a single transaction, at which point if there was a conflict the wizard restarted with up to date data. conflict detection was done by a sequential id keyed on the accounts touched on the operation, so that any operation modifying the account before your delta was applied would knock your commit off
- hinkley 10y agoBanking and the credit industry are a good example of eventually consistent systems. But you can see the inconsistencies and you're expected to just ignore them. I guess what I'm asking is how do you push back on requirements and inattentive coworkers that make these compromises unworkable, because it seems so pervasive to me.