NoSQL – Back to the Future or Yet Another DB Feature?

Re:NoSQL – Back to the Future or Yet Another DB Feature? by paperwork on Wednesday May 30, 2012 @04:00PM (#4044564)

NoSQL is giving up FAR more than ACID. It is giving up the ability to consume the stored data in a beautifully concise and expressive manner.

edit: 'the ability to'

[ Parent | on HN ]

Re:NoSQL – Back to the Future or Yet Another DB Feature? by vicaya on Wednesday May 30, 2012 @06:10PM (#4045170)

The consensus of NoSQL these days is Not only SQL. Nobody is disagreeing that SQL (and the underlying relational algebra) is expressive and general.

For a lot applications/use cases, schema free get/put/delete is a lot more concise than any SQL concoctions. Besides, using RDBMS/SQL to store/retrieve complex graph is neither beautiful or concise.

Just because you can use your Swiss army knife to kill a few roaches doesn't mean you should.

[ Parent | on HN ]

Re:NoSQL – Back to the Future or Yet Another DB Feature? by taligent on Wednesday May 30, 2012 @05:14PM (#4044913)

If my data is document based then how is SQL going to be more concise and expressive than JSON ?

Say I have a domain model that involves a primary object e.g. User with lots of maps and arrays then how is SQL going to be better then ? Lots of tables and joins better than a single document. I think not.

[ Parent | on HN ]

Re:NoSQL – Back to the Future or Yet Another DB Feature? by paperwork on Wednesday May 30, 2012 @05:35PM (#4045029)

If your data is a User object with maps and arrays, and you design a data structure which gets you the result in exactly that format, you _are_ giving up the ability to ask other questions of this data. You are giving up the ability to ask _many_ different kinds of questions (expressive) in a relatively simple way (concise).

[ Parent | on HN ]