> "Pick the right tool for the job" has been the biggest casualty in the midst of the schemaless hype we're going through right now. Even getting to the point

> "Pick the right tool for the job" has been the biggest casualty in the midst of the schemaless hype we're going through right now. Even getting to the point of realizing that most domains where NoSQL or schemaless solutions thrive are also domains where you need to be thinking in suites of persistence technology, ie where trying to choose a single data persistence technology is crazy, would be a big step. A beast like Reddit (for example), has clear areas where a document centered schemaless approach would yield big wins, but that doesn't mean it's ideal for handling their advertising billing or their master data. "The job" is quite often many smaller jobs, each of which needs it's own tool. Sometimes it's a lot easier to put on slippers than to carpet the whole world.