News for hackers. Stuff that matters.
Re:NoSQL vs. SQL: The truth about SQL, NoSQL, and NoNoSQL by Tarang on Saturday December 14, 2013 @09:46AM (#6905796)
The bias is very obvious. There is a leaning toward SQL. While some of the things may be true there is a heavy focus on standards here & less so on performance & capabilities.

Looks like its to push the commercial product on the bottom of the page.

Re:NoSQL vs. SQL: The truth about SQL, NoSQL, and NoNoSQL by sophacles on Saturday December 14, 2013 @10:42AM (#6905918)
I got lost with the "is it a * standard" comparison.

I understand the importance of standards, but a standard for a query language is different than a category of data stores. (Also - half the things he talks about further down are very very hard to do with standard SQL and not using any proprietary extensions - see Hierarchal).

Perhaps a comparison that made the left column "RDBMS" would be better... At the very least the 2 standards questions would be set to NO.

Further - there is an awful lot of stuff lumped in RDBMS vs EVERYTHING_ESLE...

"Is it based on a rock solid theory?" Well.. at the very least graph databases are. Others yes and no.

"Will it be around in t 10 years?" Again, given that Neo4J is over 10 years old already and its usage is increasing... I will place a long bet on it being around. Others... again yes and no. Similar for RDBMS. Will oracle be here? Yes. Will Postgres... again yes. But some of the Column-store SQL databases? Maybe. (Also - what does it mean for semi popular software to go away... it takes a really long time. Heck Remember the Firebird database that had some popularity ~10 years ago? turns out they are still shipping code, as of 12-7 anyway. Who knew? Who uses it?)

"Is it even a well defined concept"... Again unfair. The term NoSQL came out of a clustering based on usage, where the results were ("RDBMS/SQL", "everything else") - because at the time "everything else" was the only way to see statistical significance against "RDBMS". Of course its poorly defined. Of course with RDBMS we could be talking about a dozen different technologies with an SQL+extensions interface.

I guess i just get annoyed when people make silly arguments. Not to mention I'm too pragmatic to understand the concept of SQL vs NoSQL. They are tools. Some are good for one thing, others for other things. Seriously - if you take away my graph databases I'll get annoyed. But I'll be equally annoyed if you try to make me use them for storing interesting lookup tables when Postgres is sitting right over there.

tl;dr - We probably need to kill the NoSQL terminology. It's outlived its usefulness.

Re:NoSQL vs. SQL: The truth about SQL, NoSQL, and NoNoSQL by lukaseder on Saturday December 14, 2013 @01:07PM (#6906418)
> We probably need to kill the NoSQL terminology. It's outlived its usefulness.

On a more serious note, this is probably the main point of that website.

Re:NoSQL vs. SQL: The truth about SQL, NoSQL, and NoNoSQL by clarkevans on Saturday December 14, 2013 @09:54AM (#6905808)
JooQ is Apache 2.0 licensed. He's selling support and drivers for commercial databases.
Re:NoSQL vs. SQL: The truth about SQL, NoSQL, and NoNoSQL by mattdeboard on Saturday December 14, 2013 @09:52AM (#6905804)
This reminds me of the Stephen Colbert quote, "Reality has a well-known liberal bias."
Re:NoSQL vs. SQL: The truth about SQL, NoSQL, and NoNoSQL by sixbrx on Saturday December 14, 2013 @09:58AM (#6905812)
Depends a lot on who you surround yourself with.