My biggest problem with #NoSQL. Check out this argument against relational datastores. This is the primary argument for #NoSQL
"...and this is really why we’re looking at #NoSQL today" .
The argument for nosql is simply this. That it's computationally expensive to denormalize your data model for the view, and he argues that the only reason to normalize data is storage space optimization.
Here's the problem with this argument. You shouldn't be denormalizing your data model for the view in the first place.
If used correctly, normalized, relational data stores are not only easy on your storage, but they are easy on your network i/o, and they are easy on the eyes. This is because, if used correctly, the view is only requesting the data that it actually needs to draw the view, and the view is only drawing the data that a user is actually reviewing or mutating at a given point in time.
#sql #coding #architecture #dynamodb
"...and this is really why we’re looking at #NoSQL today" .
The argument for nosql is simply this. That it's computationally expensive to denormalize your data model for the view, and he argues that the only reason to normalize data is storage space optimization.
Here's the problem with this argument. You shouldn't be denormalizing your data model for the view in the first place.
If used correctly, normalized, relational data stores are not only easy on your storage, but they are easy on your network i/o, and they are easy on the eyes. This is because, if used correctly, the view is only requesting the data that it actually needs to draw the view, and the view is only drawing the data that a user is actually reviewing or mutating at a given point in time.
#sql #coding #architecture #dynamodb
Comments
Post a Comment