No one said that.
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.
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.