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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.