The case for NoSql is still pretty rare in 2016.
Hype Driven Development
Marek Kirejczyk
7.4K114

I think it really depends on the product you’re building… If you are creating something that will receive unfrequent updates on datas/schemas you’re absolutly right. In developing apps that are updating very fast having rigid schemas can be a problem… you can relate multiple tables, that’s true, but in just a few iterantions you will relate to a lot of tables and your query will become bigger and bigger…

Also using nosql (JSON like) will provide you a similar 1 to 1 representation of an object-data you want to store…

Also NoSQL databases are from different types and each of them provide a solution to a specific request…

To me is a lot easier building a product with NoSQL (JSON like), but depends on the RESULT you need / want to achieve…

Like what you read? Give Matteo Bombelli a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.