News for hackers. Stuff that matters.

A comment on Why The Clock is Ticking for MongoDB. Parent comment

Re:Why The Clock is Ticking for MongoDB by threeseed on Thursday April 17, 2014 @10:11AM (#7603623)
It's because a fixed schema is unnecessary in most cases. Most developers using a database are doing so via an ORM. In which case they already have a data model in their code. It often fixed and depending on the language strongly typed. It is also centralised, richer, commented, has far better validation and in source control.

So again why do I need a second data model that does nothing but get in my way ?

[ Parent | on HN ]
Re:Why The Clock is Ticking for MongoDB by pilif on Thursday April 17, 2014 @10:25AM (#7603720)
because querying and aggregating your data with arbitrary conditions becomes much easier. Using SQL you describe what result you want and let the database figure out how to retrieve it.

In many document stores, you have to write manual map/reduce jobs telling the system how to get the data you want.

[ Parent | on HN ]
Re:Why The Clock is Ticking for MongoDB by threeseed on Thursday April 17, 2014 @10:32AM (#7603798)
Most software development projects tend to be falling into two camps these days. Either they are simple and just need basic filtering/grouping in which case you don't need map/reduce. Or they are doing more advanced querying of data in which case Hadoop/Mahout is a better option.
[ Parent | on HN ]