This is gold🔥Thank you so much Arpit for bringing this! I am a college student & I have a project on CRDT. This podcast has helped me so much to learn about CRDT & Opeartional Transforms. Also Vipul, you explained things so well. Please continue this series!
small correction at aroun 11:56 , Arpit mentioned "C in ACID" in the context of strong v/s eventual consistency. but that's not "technically" correct. The C he is talking about is in the context of CAP theorem. The C in ACID is a different kind of Consistency which simply means that an ACID compliant Database will always store data in it "consistent" to the constraints, indexes, key relationships, etc. defined schematically in it. For example, if I have a user table with "email" id column and marked it with a unique constraint, then the C in ACID, which is consistency, ensures that it is 100% guaranteed that the user table will never be finally committed with duplicate emails. Here, the database is being "consistent" to the unique constraint on the email column. Rest, a great video Arpit, as always!
Shit. Did I make this blunder. Really sorry. I have been very explicit about the difference between C in ACID and C in CAP and even have an hour long video about the same. ruclips.net/video/--YbYCfMnxc/видео.htmlsi=goDfA2yH3JsOlnk5
Write through cache example just blew my mind, but, to maintain sync b/w 2 separate entities let's say Redis(cache), MySQL(database), there has to be a decentralized server, correct 🤔?
Well work with CRDT, OT is very esoteric. Throwing large information at once would only confuse people. It's better to release content in installments.
This is gold🔥Thank you so much Arpit for bringing this!
I am a college student & I have a project on CRDT. This podcast has helped me so much to learn about CRDT & Opeartional Transforms.
Also Vipul, you explained things so well.
Please continue this series!
Thanks for your comments Kshitiz!
Can you elaborate your project please ?
so many things added to list today to learn , this is the beauty of Data Engineering
Indeed. :)
small correction at aroun 11:56 , Arpit mentioned "C in ACID" in the context of strong v/s eventual consistency. but that's not "technically" correct. The C he is talking about is in the context of CAP theorem. The C in ACID is a different kind of Consistency which simply means that an ACID compliant Database will always store data in it "consistent" to the constraints, indexes, key relationships, etc. defined schematically in it. For example, if I have a user table with "email" id column and marked it with a unique constraint, then the C in ACID, which is consistency, ensures that it is 100% guaranteed that the user table will never be finally committed with duplicate emails. Here, the database is being "consistent" to the unique constraint on the email column.
Rest, a great video Arpit, as always!
Shit. Did I make this blunder. Really sorry.
I have been very explicit about the difference between C in ACID and C in CAP and even have an hour long video about the same.
ruclips.net/video/--YbYCfMnxc/видео.htmlsi=goDfA2yH3JsOlnk5
Good one! For Scala ♥ (CRDTs, OTs, Diff Merge) - convergence io, built with OriendDB. I would love to build something with Redis-like DBs.
I half expected Joseph Gentle to introduce CRDTs
It did solve my couple of confusions😌
thanks a lot , this concept made my day
Thank you i am was planning to ask you to do a video on this
Hi, could you upload these podcasts to Spotify as well? Thank you so much, and look forward to your next content!
Worth the time!
Great video
Write through cache example just blew my mind, but, to maintain sync b/w 2 separate entities let's say Redis(cache), MySQL(database), there has to be a decentralized server, correct 🤔?
You r champ regarding db
He is indeed!
Fluidframework from Microsoft uses CRDT.
So much to learn. Fantastic stuff @arpit @vipulvaibhaw
Thanks 👍 glad that you liked it.
🙏
I don't think this much detailing is good for interviews even for staff SDE's
Well work with CRDT, OT is very esoteric. Throwing large information at once would only confuse people. It's better to release content in installments.