2 ms·
Just because there's overlap in the problem domains the two classes of tools can be used for does not make them fully interchangeable. If you use a NoSQL tool
by rosser 17y ago
Just because there's overlap in the problem domains the two classes of tools can be used for does not make them fully interchangeable. If you use a NoSQL tool for transaction processing, you're probably doing it wrong; if you use an RDBMS to house vast amounts of schema-less data, you're probably also doing it wrong. Yes, exceptions exist for every rule, but in the grand Venn diagram of applicability of NoSQL and RDBMSen, there are huge areas that don't overlap. You ignore those areas at your own peril.
- wvenable 17y agoIn this case, is the data schema-less? They started with a defined schema and maybe now they don't. Your data defines the tool, but you define the data. I can store JSON in a MySQL column and you'd say I'm using the wrong tool. But I decided to define a schema instead, then I'm using the right tool? It's pretty arbitrary. Some requirements do lean one way or the other but most of the time there's not much of a difference. The areas where clearly an RDBMS is the correct solution or where NoSQL is clearly the correct solution aren't an issue. I think there are huge areas that do overlap. NoSQL is being advocated in far more situations than just where it's clearly the correct solution.