P.S.: I also find it amusing that they stored+hosted their financial ledger using MongoDB. Not that you can't commit massive financial mismanagement with any tool, but I was not a fan of the "NoSQL" evangelism of the 2010s.
P.S.: I also find it amusing that they stored+hosted their financial ledger using MongoDB. Not that you can't commit massive financial mismanagement with any tool, but I was not a fan of the "NoSQL" evangelism of the 2010s.
Embezzlement is finally web scale! [1]
(The problem here is not nosql, I believe you can do reliable accounting with ScyllaDB and Cassandra as long as you design things correctly. Basically only ever allow append/add but never allow update/delete. I’m not sure if this is true of MongoDB.)
The point is it’d be hard to loose data with Scylla as long as your only ever appending to the physical tables. I don’t know if MongoDB has this same attribute.
Things can go wrong on many layers above and below the database, so the property you describe seems like an implementation detail of one particular approach, not something fundamentally necessary for sound bookkeeping.
Are you saying it’s just as good to do this in the application layer? I respect that’s a possible option. Not sure I agree it’s a good option.
This can be, but definitely doesn't have to be, a typical relational database in conjunction with a core banking system.
I don't see what would inherently disqualify Mongo from being the backing layer for that core banking system then.
when the k8s+mongodb "non-legacy" tech stack implodes at least I have a physical document the bank produced that the court can understand
Alas, for many people the "workaround" is to put their credentials into a third-party service, and the fact that such things exist make me think I'm taking crazy-pills. [0]
https://stackoverflow.com/questions/16833100/why-does-the-mo...