Learn more about NoSQL → http://ibm.biz/nosql-guide
Check out IBM Cloud Databases for PostgreSQL → http://ibm.biz/dbs-for-postgresql
Check out Cloud Databases on IBM Cloud → http://ibm.biz/cloud-dbs-on-ibm-cloud
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.
Get started on IBM Cloud at no cost → http://ibm.biz/cloud-free
Subscribe to see more videos like this in the future → http://ibm.biz/subscribe-now
#SQL #NoSQL #CloudDBs
11 replies on “SQL vs. NoSQL: What's the difference?”
I got lost in the thoughts about – how did you make this video ? how are you writing !!
Nice video with great notes
very good explanation of the key differences thank you
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.
Each has its strengths and weaknesses and smart decision would be to employ both systems together with knowing where to store what….
Multiple questions come to my mind after looking at this very good video: thank you for that.
– To come back to your illustration with an e-commerce website: don’t you need a structured DB (SQL) to identify the products hosted in a Non-SQL DB that you will present to the consumer?
– Another comment: as No-SQL is in memory it limits its size where with SQL you can have huge size of DB. Correct?
– Also I’m curious about performances: is there a kind of index with No-SQL DB?
As I see it and you mention it at the end of the video, the combination of the 2 technologies is the key.
NOSQL was developed after SQL because of the lackings of SQL. I would always prefer NoSql
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…
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.
Good effort, but needs some more depth. The way is explained, makes a classic Oracle DB qualifying as NoSQP DB 🙂