SQL vs. NoSQL: What's the difference?

There are many databases available in the market, and knowing which one to choose can be extremely difficult.

In this lightboard video, Jamil Spain with IBM, breaks down the top 5 differences between SQL and NoSQL databases to help you make a better informed decision when selecting a database to use.

#SQL #NoSQL #CloudDBs

[sndselecta]

The example at the end for me was a great explanation. Finally understand a simplistic implication. To further on this: a user is logged in, the cart is all products being purchased or a favourites section, which will all be persisted to storage (HD). The transient (or constantly changing) data could be the session data (login duration day, week, month stats), product browsing history, of that user, but wouldn't this be also stored at a later point? The cart and favourites data is used by both user and supplier, but the session data is usually only used by supplier for analytics, targeted promotions, predictive data modelling (other product suggestions etc) etc...From the users POV might not be large but from a Product POV could be huge.

[carlosdegollado]

WOAH! I've been thinking so hard trying to figure out which one I should implement when I completely forgot that there is the option of both....Thank you for helping me see that.

[Flankymanga]

Each has its strengths and weaknesses and smart decision would be to employ both systems together with knowing where to store what....

[VivekYadav-vklh]

I got lost in the thoughts about - how did you make this video ? how are you writing !!

[chillbro]

Wow interesting last point! I remember facing dev situations and feeling like a limitation of some sort, but perhaps taking a NoSQL approach would have lifted that. Quite exciting. There's a couple of teasers in here that i'd like more information on. Like what is vertical scaling, what is horizontal scaling? And what accessing NoSQL looks like? But i definitely feel certain of the mode of SQL and the mode of NoSQL enough to experiment with NoSQL.

[johnlaurencepoole]

I think addressing performance of a query should be a major factor. I'm SQL trained and do not know how one performs extraction of data from a no-sql data pool other than perhaps by the Linux commands "awk" and "grep". Is there a performance savings by mapping everything into SQL vs. leaving stuff in a blob?

[lawrencegatley]

Thank you! this is the perfect video for explaining the difference to me

[shriramvenu]

good job on these explainer videos IBM!

[hatimshahera]

how do they write the things in front of them? It means they are writing the other way around right? or what? I have been trying to watch the tutorial but my head is stuck at that

[BillaCode]

can we use NoSQL in Customer relationship management systems

[WojciechowskaAnna]

how can you compare "non sql" without proper definition? Time series dbs are no-sql nd they do not follow your observations?

[tw]

very good explanation of the key differences thank you

[RU-qvjl]

The problem I see with your explanation is that SQL is just a language. There are an ever increasing number of options to scale out RDBMS systems. Also it’s not like, for instance, Postgres is bad at handling JSON data with JSONB. There are some attributes that you are likely to always want to have, and some that may change per instance. So something like a table with a JSONB column is a nice approach. However, I wouldn’t go around installing Postgres on loads of mobile phones for kicks. It’s just not reasonable to use that amount of storage space.

Just a thought.

[samjones]

Excellent explanation sir! Thank you very much! Cheers!

[w]

I am curious about "Vertical vs. Horizontal Scaling"

1. Why can I not scale SQL Databases Horizontally? You *could* use sharding and read replicas improve scaling needs - sure, it requires work, but SQL is constantly improving - isn't that right?
2. What I can see is - you can easily make changes in NoSQL e.g. unstructured - which is quite costly in SQL

[JanacMeena]

SQL
- More pre-planning required
- Vertical scaling
- Better for multi-row transactions

NoSQL
- Horizontal scaling
- Unstructured

[jtaylor]

This could have been easier to follow - in some parts you are using IT buzzwords to describe an IT buzzword concept - which is even more confusing. It would be a lot simpler to understand if you could use plain English and examples - so, for example, what does horizontal and vertical scaling actually mean, what does 'dynamic' as point 4 on the No SQL side of your diagram actually mean.

In the first few sentences of the presentation you mention that it might be surprising that people ask questions about these differences between technologies, or that there is confusion about the differences, but in my mind it's not surprising at all when the meaning of the buzzwords/language used to actually explain the differences are unclear.

[LoneLeagle]

SQL requiring more memory & computing power is making me lean more toward NoSQL because that means hosting is cheaper for NoSQL apps.

[nk-thn]

I don't get what you mean by NoSQL is all in memory, isn't it also have to persist data on disk, like MongoDB...

[dovasd]

Good effort, but needs some more depth. The way is explained, makes a classic Oracle DB qualifying as NoSQP DB :)