4 ms·
I suspect that we are discussing one of those "if all you have is a hammer" cases here. In my experience most enterprise applications will prefer to have data i
by Pamar 5y ago
I suspect that we are discussing one of those "if all you have is a hammer" cases here.
In my experience most enterprise applications will prefer to have data in tabular form because making financial or management reports (including dashboards and analytics) based on a serialized portion of a program's heap is not really suitable.
Maybe I am just not "modern" enough.
- gryn 5y agoI've got to agree with you. after the initial team that designed such document based system have gone to other jobs, once it got harder. I found my self maintaining and evolving such system need to the changing needs of the business. I've had to deal with the cases where customer were charged multiple times, some that were never charged at all, and all kind of similar problems. I can trace almost all of them back to the original decision of lets just ditch a traditional DB for a NoSQL one, because it scales TM and geo redundancy will be easier for our infrastructure team.
- jhgb 5y ago> just ditch a traditional DB for a NoSQL one, because it scales TM and geo redundancy will be easier for our infrastructure team. This doesn't sound like it has anything to do with the data model, though. The so-called "NoSQL" databases can be deficient for many other reasons.
- jhgb 5y agoLarge-scale enterprise applications will generally favour the relational model simply because it's application-independent (which is something you're pointing out at the end). But documents are documents, they already have some defined structure, mostly a tree-like one.