I link this video to anyone who is beginning with Cassandra. You have the most clear and concise explanations available online. Thank you very much for your work!
@irtizahafizАй бұрын
I really appreciate it. Thank you!
@danser_theplayer01Ай бұрын
11:50 let me clarify, this is a very compound PRIMARY KEY with a PARTITION KEY ?
@brianpack369 Жыл бұрын
I am now on course to crash a Cassandra database.
@nexus8884 ай бұрын
6:47 so a write goes to all partitions or just one? You didn't mention this. If only one partition receives the write, is it written to disk before committed back as successful to the caller or how does this work?
@10yearsago8410 ай бұрын
Really loved the explanation !!
@alaad1009 Жыл бұрын
Excellent video man !
@irtizahafiz Жыл бұрын
Glad you liked it!
@haneulkk Жыл бұрын
It was so easy to understand! Thank you!
@dineshkuruba18802 жыл бұрын
great video, please do a video on how the data is stored on disk with different column families
@irtizahafiz2 жыл бұрын
Good idea. I will!
@tianqizhang1573 Жыл бұрын
Great explanation, easy to understand!
@letsCherishCoding Жыл бұрын
Amazing explanation!!
@athulraveendran757 ай бұрын
Great explanation ❤
@josedamianjimenezn8892 Жыл бұрын
Very clear your explanation!, Now I can see that cassandra is a good option to consider as DB in my project, thanks a lot for this useful content!
@irtizahafiz Жыл бұрын
Glad this helped you come to that conclusion.
@unujjwalАй бұрын
Mentioning the consistent hash ring should be a necessity for intro to cassandra videos
@h.mantri6 ай бұрын
When the data is still in Memtable and not yet sent to SSTable and server crashes (or say power goes off), we loose data right? What happens in those cases? Any way to recover data?
@fifamobile-xx2ef6 ай бұрын
first written to the commit log to prevent data loss in the event of a failure. And i'm working on ScyllaDB; So if i know something let you know
@Sverdiyev6 ай бұрын
I’ve also wondered about that. But it seems that the commit log is on disk, similar to WAL. So it would rebuilt from that. The more interesting question here is conflict resolution between the nodes in case of conflicting writes and how is the data replicated between the nodes. Classic distributed system issues it seems.
@ankita.mantrii6 ай бұрын
@@Sverdiyev If commit log were on disk, it would defeat the original statement that "cassandra writes are fast since they are written to in-memory commit logs"
@irtizahafizАй бұрын
Thank you!
@mpaltanwale2 жыл бұрын
Commitlog is on disk and not in memory, if you want to make correction in the video.
@irtizahafiz2 жыл бұрын
Uggh, yeah that's right. Thank you for correcting.
@Khushboo1811 Жыл бұрын
@@irtizahafiz And sequential writes to disk are very fast, that's why even if CommitLog is not in memory, writes are still very fast
@rajesh436110 ай бұрын
@@Khushboo1811 it actually does the bulk update to Disk..every 10seconds if i am not wrong.
@motazhejaze387 ай бұрын
many thanks
@breaknbroke2 жыл бұрын
Is a distributed database all you need for a system to be distributed?
@irtizahafiz2 жыл бұрын
I think you can use the term in this case, yes.
@Entertainment_Zone25222 жыл бұрын
Bro can you please make video on zipkin traces Store in Cassandra database
@irtizahafiz2 жыл бұрын
Added to my backlog. Thanks for the idea!
@catalinim42272 жыл бұрын
multiple players with the same name with the same club? ... 😵💫what?
@irtizahafiz2 жыл бұрын
That analogy fell apart very quickly LOL. But hopefully you get an idea of how the different keys work.