@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.

@carlosdegollado7687

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....

@JanacMeena

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

NoSQL
- Horizontal scaling
- Unstructured

@prashantkumar6342

I appreciate your writing skills more

@VivekYadav-vk2lh

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

@jerrydeck7071

This is JEROME ROBINSON and I have to admit that  at first programing was so Confusing to me BUT NOW after practicing  it everyday I've developed a Love for it ! Programing i and Mathrmatics are so ENJOYABLE to me ( message from Jerome Robinson )

@lawrencegatley6157

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

@shriramvenu

good job on these explainer videos IBM!

@SohviHaukkala

Very clear! Thank you👌

@mrard-v4e

Well explained, thanks ❤

@ndeedd

The way he wrote is even more impressive 😮

@LoneLeagle

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

@duckyguy1147

i like this ibm sessions

@eddebrock

The person who understands what he's saying already knows the answer to the question.

@amosadesokan2045

Thanks for the clear clarifications

@jtaylor8606

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.

@chillbro2275

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.

@rahimeinollahi1

Nice video with great notes

@samjones0320

Excellent explanation sir! Thank you very much! Cheers!:goodvibes: