Published: Dec 28 2010 / 02:50
Nice article and good tip.
NoSQL is not just about scale, take CouchDB for example
The article is not comprehensive, but I think the points made are strong.
We need a compiler that converts SQL into NoSQL program code
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.
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.
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.
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.
Arguments seem dubious and superficial to me: you should not use NoSQL because you shoulda learn it ?!!!
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.
Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.
Advertising - Terms of Service - Privacy - © 1997-2014, DZone, Inc.