Why and how NoSQL databases can scale 'infinitely' | Understanding NoSQL and partitioning

preview_player
Показать описание
CORRECTION: When I said Google Spanner I meant Google Cloud Datastore*

Hello everybody I'm Nick and in this video I will explain everything that you need to know about how NoSQL databases scale. It's a very interesting topic and once you understand how they scale you can understand how you can design them better.

Don't forget to comment, like and subscribe :)

Social Media:

#scale #nosql #databases
Рекомендации по теме
Комментарии
Автор

Hi Nick, I discovered your channel only yesterday and I've already watched significant part of all the content you generously share with us, just because I can't stop, really, so amazing! Please just don't stop, keep coding and share with us :) I'd love to see more videos on .NET Core, Microservices and distributed systems. Last years I was doing so called Modular Monolith apps, and recently started looking towards Microservices Architecture. It's so complicated, there're so many ways to do it wrong, so videos like you do are extremely useful and helpful. Thank you very much!

rustamhajiyev
Автор

We love to see your take on NoSQL approach!

DerekWelton
Автор

Would love you see you take two application scenarios (one that is suitable for RDBMS and one that would be better handled with NoSQL) and just break down how you would go about finding which way would be better, and then ultimately go through designing the DB for each scenario.

vishnugovindan
Автор

Thanks, It'd be great to have a video about NoSQL DD.

ericserafim
Автор

Hello Nick, I took the time to see all your videos during this month and I will really appreciate a dedicated video on NoSql.
Thank you for all them :)

benjaminhaddad
Автор

Hi Nick,
Great video! Please do one on the NoSQL data design.

TheYaamu
Автор

The best explanation I've come across so far. As a beginner in this field, I thank you.

alikibao
Автор

Great tutorials thank you sir,
We would definitely want a NoSql database design video

ahmedrazzak
Автор

Great insight into what happens behind the scenes for scaling horizontally. Loved the content and articulation. 👏🏼

nishadkumar
Автор

Hi Nick,
Thanks for the video. Would love to see NoSQL database design video.

abhishek
Автор

Would love to see a follow-up no-sql design video

GiovanniOrlandoi
Автор

I need to scale mongo for millions of users and this is giving me a good starting point

notafakeemail
Автор

isnt the partition key simply what a well chosen primary key in relational databases would be? so what makes NoSQL different than relational databases except for the way less strict schemas?

lancej.
Автор

So the partition key is the only value you can query (efficiently) at scale? And there's only one partition key per container?

danieljayne
Автор

hi nick . thank you for your amazing video . can create video for design patterns ?

salarzardouz
Автор

Google Cloud Spanner is google RDBMS SQL db, I think you meant Google Cloud Datastore a NOSQL Db from google.

paragsarin
Автор

why i can't use youtube auto translate to English in this video ?

cuno
Автор

Hi Nick, thanks for your video!
It would be great to see this partitioning in practice!
Dou you have courses about ASP.NET Core, Docker and other technologies from this stack on Udemy or Pluralsights?
I will be happy to buy and watch them!

antonoreshko
Автор

Hello, Nick. I have used SQL databases before for my ASP.NET Core projects, but I wanted to switch to MongoDB.
I wanted to migrate my database to MongoDB and used a library that makes it really easy to work with MongoDB in .NET and even supports Many-to-Many relationships.
But the relationship part of the library (even One-to-Many) seems to work slower than SQL counterparts.
So here comes the question.
Is the performance worse, because my database design is not appropriate for NoSQL or could it be performance issues in the library I am using?

And for that reason, I would really love your explanation on how should a NoSQL database be designed. And if you can, please include One-to-Many and Many-to-Many relationships in your example.

autoplanet
welcome to shbcf.ru