News for hackers. Stuff that matters.
Re:How NoSQL forced the evolution of a scalable relational d... by threeseed on Friday July 13, 2018 @05:40AM (#17521613)
So it's okay for developers to build their own database for their specific use case. But it's not okay for developers to use a database for their specific use case.

Makes sense.

Re:How NoSQL forced the evolution of a scalable relational d... by orwin on Friday July 13, 2018 @06:06AM (#17521697)
This is not what he said. He basically said that in many cases, some developpers pushed something like mongo, ES or cassandra in their project or even company when a small sqlite or an effective postgressql were much more appropriate.

Specific databases solve specific problems. In my current company, for log storage and analysis, InfluxDB was our solution after testing both ES and postgress, but we did compare all the products, and we still do as we expand. In my previous company, the main database in the product was Zope. I agree that mongoDB may be better in some use case, but i strongly doubt that most company are running it because it's the most appropriate product.