Why are joins not possible in NO-SQL Databases ? | SQL vs NO-SQL | Arpit Bhayani | Part 2

  Рет қаралды 2,695

Sukhad Anand

Sukhad Anand

Күн бұрын

Why are joins not possible in NO-SQL Databases? | Similarities and Differences | SQL vs NO-SQL | Arpit Bhayani | Techie007
Hello everyone,
Welcome back. This is part 2 of the podcast with ‪@AsliEngineering‬ in which we discuss more on SQL and No-SQL databases. We left part 1 on a cliffhanger where we were discussing why are joins not possible in No-SQL databases. Let's find out.
Connect with Arpit on LinkedIn: / arpitbhayani
Subscribe to his channel: / @asliengineering
#softwaredevelopment #sql #mongodb

Пікірлер: 30
@rjarora
@rjarora Жыл бұрын
With all due respect, you should stop all the 'Umm', 'Hmm' etc, that you do while the speaker is talking. It isn't very pleasant and hampers the whole flow.
@Techie007
@Techie007 Жыл бұрын
Thanks for the feedback.
@duredurrani
@duredurrani Жыл бұрын
Video on How KZbin vanced and brave browser works? How are blocking ads? And why YT is not doing anything about that?
@Techie007
@Techie007 Жыл бұрын
Will do
@Nightaxeblade
@Nightaxeblade Жыл бұрын
Firstly great video. I did not understand the line that sql without foreign keys/constraints is similar to nosql. Maybe, some explanation or deeper dive on that with an example maybe.
@Techie007
@Techie007 Жыл бұрын
It is simply because if there is no foreign key, then joins in SQL won't be possible the way they are today. You would have to do a join like you would do in No-SQL. Bring data from 2 tables and join them yourself.
@rkisdp
@rkisdp Жыл бұрын
How Google Spanner combines NoSQL and SQL traits? How it ensures ACID along with CAP even after being a NoSQL database?
@adarshverma3372
@adarshverma3372 Жыл бұрын
Very informative questions, Looking for more content like this
@Techie007
@Techie007 Жыл бұрын
Thank you so.much Adarsh.
@anubhavtarar7096
@anubhavtarar7096 Жыл бұрын
What about we have say cassandra just one node cluster then join should be possible atleast?
@pollathajeeva23
@pollathajeeva23 Жыл бұрын
Great discussion on SQL & NoSQL transactions. Some simple terms to add on: SQL -> Transaction, CP, Master Slave, Raft NoSQL -> No-Transaction, AP, Active-Active geo distribution, CRDT NewSQL -> New-Transaction, CAP, Distributed, YugaByteDB
@Techie007
@Techie007 Жыл бұрын
Thanks for sharing.
@kirtigupta6090
@kirtigupta6090 Жыл бұрын
I got confused in the part where earlier we said that SQL DB in a Master-Slave architecture is eventually consistent due to asynchronous replication but then we also recommended using SQL DB if ACID compliance is needed. SQL DB in a Master-Slave architecture is very a common use-case and if we cannot guarantee ACID properties with it, then it makes SQL DB very restrictive in terms of the highly claimed ACID properties associated with it.
@Techie007
@Techie007 Жыл бұрын
In most of the business use cases, you don't need strong consistency. Eventual consistency with read replicas serves the purpose. But if you want ACID, then it restricts SQL DB to single node and hence vertically scalable.
@rkisdp
@rkisdp Жыл бұрын
@@Techie007 But what about big banks like SBI, where you have to have strong consistency and data is also huge?
@akshaytakkar6747
@akshaytakkar6747 4 ай бұрын
@@rkisdpeven financial transactions are not consistent..there is always a nightly settlement of all transactions where they can be considered committed
@duredurrani
@duredurrani Жыл бұрын
Video on How KZbin vanced and brave browser works? How are blocking ads? And why YT is not doing anything about that?
@Techie007
@Techie007 Жыл бұрын
Will do
@abhinavghosh725
@abhinavghosh725 Жыл бұрын
if SQL DBs are inherently used for ACID use cases and are predominantly single node ( compared to NoSQL which are mostly distributed ), doesnt it make SQL inherently less scalable by design, as you are restricted to a single node and hence can only do vertical scaling ? P.S - great video btw , interesting topic !
@Techie007
@Techie007 Жыл бұрын
Sometimes, we can tolerate eventual consistency even though we still want to use the interface provided by sql in terms of relationships. So, we drop the consistency constraint and use it. Considering if we need ACID, then it is just vertically scalable.
@thakararkeval4759
@thakararkeval4759 Жыл бұрын
Both Part is Awesome👋👋👋
@Techie007
@Techie007 Жыл бұрын
Thank you so much :)
@mahanteshambali
@mahanteshambali Жыл бұрын
Amazing conversation. Thank you for posting this.
@Techie007
@Techie007 Жыл бұрын
Glad you enjoyed it!
@vikastangudu712
@vikastangudu712 Жыл бұрын
Awesome.... Just Awesome..
@Techie007
@Techie007 Жыл бұрын
Thank you so much 😀
@keshavmishra2397
@keshavmishra2397 Жыл бұрын
I really enjoyed watching the videos on databases, both Part 1 and Part 2 were fantastic.
@Techie007
@Techie007 Жыл бұрын
Thank you so much.
@aayushjain1890
@aayushjain1890 Жыл бұрын
Awesome 👍
@Techie007
@Techie007 Жыл бұрын
Thanks 🤗
The Birth of SQL & the Relational Database
20:08
Asianometry
Рет қаралды 201 М.
iPhone or Chocolate??
00:16
Hungry FAM
Рет қаралды 43 МЛН
Стойкость Фёдора поразила всех!
00:58
МИНУС БАЛЛ
Рет қаралды 4,5 МЛН
Everything you need to know about CockroachDB w/ Ben Darnell | Ep 6
1:30:03
Database Sharding and Partitioning
23:53
Arpit Bhayani
Рет қаралды 87 М.
Database Indexing for Dumb Developers
15:59
Laith Academy
Рет қаралды 61 М.
This is why understanding database concurrency control is important
9:05
Database Sharding in 200 Seconds
4:43
PlanetScale
Рет қаралды 24 М.
Why do databases store data in B+ trees?
29:43
Arpit Bhayani
Рет қаралды 39 М.
Solving one of PostgreSQL's biggest weaknesses.
17:12
Dreams of Code
Рет қаралды 197 М.
The Tragedy of systemd
47:18
linux.conf.au
Рет қаралды 1,1 МЛН
What Comes After Microservices? • Matt Ranney • YOW! 2016
45:14
GOTO Conferences
Рет қаралды 9 М.
iPhone or Chocolate??
00:16
Hungry FAM
Рет қаралды 43 МЛН