Link Details

Link 536447 thumbnail
User 199388 avatar

By glamdring
via techblog.bozho.net
Published: Dec 28 2010 / 02:50

The NoSQL hype is omnipresent. And many startups are tempted to go for Cassandra/MongoDB/HBase/Redis, whatever. Here I’ll argue why they should rather stick to a SQL solution – MySQL or PostgreSQL.
  • 27
  • 4
  • 6938
  • 94

Comments

Add your comment
User 338269 avatar

Miloskov replied ago:

1 votes Vote down Vote up Reply

Nice article and good tip.

User 233461 avatar

antych replied ago:

0 votes Vote down Vote up Reply

NoSQL is not just about scale, take CouchDB for example

User 261835 avatar

Kenneth Downs replied ago:

0 votes Vote down Vote up Reply

The article is not comprehensive, but I think the points made are strong.

User 393686 avatar

RawThinkTank replied ago:

0 votes Vote down Vote up Reply

We need a compiler that converts SQL into NoSQL program code

User 261835 avatar

Kenneth Downs replied ago:

1 votes Vote down Vote up Reply

Raw: I've been thinking through how to do that. Check my blog after the new year, I will post about an open-source schema handler that I've got, and I've been pondering for a couple of weeks how to warp it to this task.

User 393686 avatar

RawThinkTank replied ago:

0 votes Vote down Vote up Reply

Obviously its not impossible but its not easy either since its not a RDBMS. But i am sure once humanity heads that way it will be the preferred way, something like LINQ i guess but actually generated code.

User 53369 avatar

behrangsa replied ago:

0 votes Vote down Vote up Reply

Most NoSQL databases have limited support for transactions. No matter how much of SQL can be translated to NoSQL, in the end with the absence of transactions it won't be complete.

User 393686 avatar

RawThinkTank replied ago:

0 votes Vote down Vote up Reply

The idea is not to create a complete replacement for RDBMS but to use queries instead of code with whatever capability NoSQL has.

The other important point is to maintain a standard , without a good standard it wont work since every new NoSQL warper will create its own syntax and fragment this idea.

User 502193 avatar

asksuperuser replied ago:

0 votes Vote down Vote up Reply

Arguments seem dubious and superficial to me: you should not use NoSQL because you shoulda learn it ?!!!

User 199388 avatar

glamdring replied ago:

0 votes Vote down Vote up Reply

No. But you would agree that the decision between learning curve vs no learning curve, if timing is crucial, leans towards no learning curve. Anyway, the point was (as I specified in the comments under the post) that people should be careful not to choose NoSQL for the wrong reasons.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Debugging JavaScript
Written by: Ashutosh Sharma
Featured Refcardz: Top Refcardz:
  1. Design Patterns
  2. OO JS
  3. Cont. Delivery
  4. Java EE7
  5. HTML5 Mobile
  1. Java EE7
  2. Spring Annotations
  3. Git
  4. Java
  5. REST