nosql database is the norm these days and yet RDMBS databases like mysql, sqlite and sql-server are very much relevant too.
Most popular open source CMS and apps like wordpress, drupal, Magento, Craft CMS, etc. continue to use an RDBMS database rather than nosql one.
What kind of apps have you developed where nosql had come useful (and there was a better case or argument for using it against RDBMS for reasons)?
Do you think nosql databases are still suitable for traditional apps like ERP/CRM/FAS? Why and why not?
Top comments (2)
I worked on an app that provides drag and drop functionality, with a very dynamic data structure. This use-case worked very well with NOSQL.
Honestly outside of that single place where there is dynamic data, an SQL approach still makes sense. I could also see a situation where the same drag and drop setup could of been done with an SQL setup.
Honestly NOSQL's best feature is its own downfall, which is its flexibility. Yes you can change your database data at any-time, but that also means you need to manage your data schema at a higher level, and manage changes/differences with the data saved.
Forcing yourself to define an SQL design upfront forces you to be honest with how the data will be managed. NOSQL just throws that out the window for better or worse.
i am currently studying nodejs with nosql database