Similarly, in the day and age of data coming in from a variety of devices with a wide range of data types, being able to store data in a more flexible format seems to make a lot of sense. A format which should be dependent on your application's access pattern and not necessarily a rigidly formatted data model that has to fit into an existing table structure.
This is what is wrong with Web Development today. NO, your Database should not mirror your application logic. Your database is a storage layer for information. You have APIs for accessing it the way you want to do it.
As a side note, a NoSQL DB does not make it easier to develop if you have different access patterns encoded in your data. Instead of knowing what is in your database (aka your schema), you have nothing but application code of X different apps that throw arbitrary JSON in your DB
In general there are little reasons to use a NoSQL Database. Those are basicly having large BLOBs and not much else. Note that this does not include Graph databases, as those have a lot of valid use cases like a social graph, etc.
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.
This is what is wrong with Web Development today. NO, your Database should not mirror your application logic. Your database is a storage layer for information. You have APIs for accessing it the way you want to do it.
As a side note, a NoSQL DB does not make it easier to develop if you have different access patterns encoded in your data. Instead of knowing what is in your database (aka your schema), you have nothing but application code of X different apps that throw arbitrary JSON in your DB
In general there are little reasons to use a NoSQL Database. Those are basicly having large BLOBs and not much else. Note that this does not include Graph databases, as those have a lot of valid use cases like a social graph, etc.