re: When to choose NoSQL over SQL? VIEW POST


Great summary! I've always been a huge fan of The CRUD aspects of SQL and the power of the data access language itself. Some of the added required constraints of a relational database add complexities, at times unnecessarily. NoSQL is great for fast, agile development, but, like you mention, it can lead to issues when data needs to be accessed in indirect methods. I've always pushed for database with SQL support in projects I've worked on due to the power of the query language itself. Because of that, it's now one of my top priorities at HarperDB to ensure that we offer full SQL support on top of our NoSQL database to blend together what we see as the best of both worlds.


Thanks for adding such insightful comment, Jacob! This sums up as a smart job now ... a proper balance of both the databases adds to lot of performance and other unsung benefits. Awesome!! 🙌

code of conduct - report abuse