SQL vs. NoSQL Databases: What’s the Difference?

#1

Post by rockdiesel » Thu, May 12, 2016, 3:45 PM UTC

SQL vs. NoSQL Databases: What’s the Difference?
upwork.com

Re: SQL vs. NoSQL Databases: What’s the Difference?

#2

Post by yamadapc » Thu, May 12, 2016, 4:07 PM UTC

SQL...?

Re: SQL vs. NoSQL Databases: What’s the Difference?

#3

Post by gjolund » Thu, May 12, 2016, 4:16 PM UTC

I have issues with his "Reasons to use NoSQL"

* Making the most of cloud computing and storage

There are plenty of "cloud" hosting options for SQL databases, enough that a simple google search should make my point for me.

* Rapid development

This is a really common reason that I have heard for wanting to use NoSQL databases. It is flat out wrong.

While NoSQL databases may not force you into a schema for your database, you will pay a toll for this mutability in your application layer.

I have worked on several NoSQL backed projects, and nearly without fail development speed drops like a rock once you make changes to the way your data is persisted.

SQL migrations may seem tedious, but the process of planning your data model and having rigid definitions for your data types saves you huge amounts of time in the long run.

Data is the foundation of most applications, and if you can't rely on your data then you are building your application on sand.

Re: SQL vs. NoSQL Databases: What’s the Difference?

#4

Post by neo2001 » Thu, May 12, 2016, 4:19 PM UTC

Grabs popcorn

Re: SQL vs. NoSQL Databases: What’s the Difference?

#5

Post by nthacker » Thu, May 12, 2016, 4:20 PM UTC

This talk by Martin Fowler is a fantastic overview into the SQL vs NoSQL discussion : https://www.youtube.com/watch?v=qI_g07C_Q5I

Re: SQL vs. NoSQL Databases: What’s the Difference?

#6

Post by hardwaresofton » Thu, May 12, 2016, 4:20 PM UTC

Postgres is the last SQL DB thing mentioned?

No mention of RethinkDB (https://rethinkdb.com/) ?

SQL is good if your data is "unchanging"? Schema migrations happen, SQL can be sharded and scaled to multiple servers, and the fact is, unless you're facebook or google, you probably won't even need it. Didn't reddit run postgres since it began?

Glad I skimmed this.

Re: SQL vs. NoSQL Databases: What’s the Difference?

#7

Post by jxcl » Thu, May 12, 2016, 4:25 PM UTC

gjolund wrote: post #3

I have issues with his "Reasons to use NoSQL" * Making the most of cloud computing and storage There are plenty of "cloud" hosting options for SQL databases, enough that a simple google search should make my point for me. * Rapid development This is a really common reason that I have heard for wanting to use NoSQL databases. It is flat out wrong. While NoSQL databases may not force you into a schema for your database…

I also love the "Reasons to use SQL":

> If your business is not experiencing massive growth that would require more servers and you’re only working with data that’s consistent, then there may be no reason to use a system designed to support a variety of data types and high traffic volume.

This whole article seems heavily NoSQL biased. I don't know what qualifies as high traffic volume, but Postgres has been known to handle 500,000 transactions per second, and there is stuff in the pipeline that is only going to make that faster.

http://akorotkov.github.io/blog/2016/05/09/scalability-towar...

Re: SQL vs. NoSQL Databases: What’s the Difference?

#8

Post by overcast » Thu, May 12, 2016, 4:25 PM UTC

hardwaresofton wrote: post #6

Postgres is the last SQL DB thing mentioned? No mention of RethinkDB ( https://rethinkdb.com/ ) ? SQL is good if your data is "unchanging"? Schema migrations happen, SQL can be sharded and scaled to multiple servers, and the fact is, unless you're facebook or google, you probably won't even need it. Didn't reddit run postgres since it began? Glad I skimmed this.

Yeh seriously RethinkDB is the perfect hybrid of "NOSQL" document storage, with SQL like relationships. Been using it for all my projects the past year, and I love it.

Re: SQL vs. NoSQL Databases: What’s the Difference?

#9

Post by hobs » Thu, May 12, 2016, 4:25 PM UTC

Chuckling at: Your data is structured and unchanging. If your business is not experiencing massive growth that would require more servers and you’re only working with data that’s consistent, then there may be no reason to use a system designed to support a variety of data types and high traffic volume.

SQL Databases support a variety of data types and high traffic volume, they just dont allow you to change things without thinking a little more deeply on the problem.

This article is just fluff.

Re: SQL vs. NoSQL Databases: What’s the Difference?

#10

Post by systems » Thu, May 12, 2016, 4:28 PM UTC

yamadapc wrote: post #2

SQL...?

not really, sql is usually used to refer to relational databases (and yes i am aware that sql is not fully relational)

to sql vs nosql

is more like relational vs other models

nosql can also be seen as domain specific databases some nosql options work great for specific types of apps but not others

and to conclude, the key feature of relational databases is integrity, your data is normalized, so you are guaranteed integrity, problem is, integrity is not free, this why we need nosql and other bi solutions like olap cubes

but olap cubes are different, since they dont replace relational databases, they complement each other ... olap can also be seen as domain specific