News for hackers. Stuff that matters.

A comment on NoSQL No More. Parent comment

Re:NoSQL No More by jt2190 on Friday April 11, 2014 @04:36PM (#7575459) 

  > Now you take the orders of each user and also put them 
  > into the document belonging to the respective user.
So the database doesn't force anything. The data modeler makes a questionable decision.

  > All interesting problem domains just don't fit the idea 
  > of piece of JSON without references, internally or 
  > externally.
These databases won't prevent data modeling using references, they just often don't provide as much support as a relational database does for doing joins or enforcing key constraints.
[ Parent | on HN ]
Re:NoSQL No More by danbruc on Friday April 11, 2014 @05:35PM (#7575760)
But that's my point - either you use documents in the way they are advertised and get redundancy or you normalize into many documents with relationships between them and then your documents just degenerate into entities.

I am not saying there are no usecases where a document oriented model fits well, but I argue that it is not a good fit for modeling your average business.

[ Parent | on HN ]
Re:NoSQL No More by jt2190 on Friday April 11, 2014 @07:37PM (#7576219)
I'm guessing that "the way [documents are] advertised" refers to some of the "hello world"-style examples that are found in various blogs. I'll agree that in their enthusiasm for showing how easy it is to use put data into and retrieve data from a document store (no O/R mapping!) they assume that the reader is well-versed in data modeling. This has bitten numerous inexperienced developers. I've never seen an article recommend against data normalization though.
[ Parent | on HN ]