News for hackers. Stuff that matters.

A comment on A Year of MongoDB. Parent comment

Re:A Year of MongoDB by jshen on Friday May 10, 2013 @09:23PM (#5689398)
"till it reached some kind of moderate scale where I realized it was a terrible choice going with a NoSQL db (Sometimes, I'd have to duplicate data because there were no Joins, etc)"

That statement doesn't make sense to me. One of the first things you do with a sql database when you reach moderate scale is denormalize data so you don't have to do joins, or shard which prevents a lot of joins. Joins are super convenient, but they don't scale.

[ Parent | on HN ]
Re:A Year of MongoDB by marcosdumay on Friday May 10, 2013 @10:05PM (#5689464)
You denormalize SOME joins.

On nearly all of the cases, they are very usefull, but once in a while one of them gets too slow, so you make a bit more of work enforcing the consistence by hand, accepts a bit more of risk, and denormalize it.

Throwing all of them away because a few may create problems later is a bit of an over reaction.

[ Parent | on HN ]
Re:A Year of MongoDB by jshen on Saturday May 11, 2013 @12:15AM (#5689695)
How many joins do you think this page uses? A denormalized version that doesn't scale probably uses 25-50. I'll bet the scalable implementation uses close to zero.
[ Parent | on HN ]