3 ms·

Just because you can pound a screw into the wall with a hammer doesn't mean it solves the same problem as a screwdriver.

wvenable 17y ago
And just because you've got a clever saying doesn't mean we aren't just dealing the two different kinds of screw drivers. That's the whole point here.
- 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 ago
    In 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.
- josephruscio 17y ago
  My point wvenable, is that we are absolutely not dealing with two different kinds of screw drivers here. Yes they both store "data", but there are types of data that one is well suited to deal with, and alternative types of data that the other one is better for. On my team we've already split out data into two sets, one that lives in ACID RDBMS and one that lives in NoSQL. If you are dead set in using one solution for everything, my pity for you.

wvenable 17y ago

And just because you've got a clever saying doesn't mean we aren't just dealing the two different kinds of screw drivers. That's the whole point here.

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 ago
  In 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.
josephruscio 17y ago
My point wvenable, is that we are absolutely not dealing with two different kinds of screw drivers here. Yes they both store "data", but there are types of data that one is well suited to deal with, and alternative types of data that the other one is better for. On my team we've already split out data into two sets, one that lives in ACID RDBMS and one that lives in NoSQL. If you are dead set in using one solution for everything, my pity for you.