Cassandra Database Crash Course

In this video, I will go over the basics of one of the most popular NoSQL databases, Cassandra. Cassandra is an always available, distributed, NoSQL database.
At first I will go over the features of Cassandra. From there, we are going to dive deeper and see how a read and write path works in Cassandra. Finally, we are going to go over how to design data models in Cassandra effectively. Then, we will wrap up with some good use cases of Cassandra.
I talk about all the different features of Cassandra and how they are beneficial. It’s a good introduction to Cassandra, if you want to use this database in your next application.
Here are some good resources that I wrote that will help you understand Cassandra better:
[Why are Cassandra writes so fast](blog.devgenius.io/why-writes-...)
[How does Cassandra Tombstones work](blog.devgenius.io/cassandra-t...)
[Cassandra Data Models](levelup.gitconnected.com/desi...)
[Cassandra Partition Keys vs Clustering Keys](blog.devgenius.io/cassandra-p...)
Cassandra official docs
[Cassandra Docs](cassandra.apache.org/_/index....)
#cassandra #database
Visit me in: irtizahafiz.com
Reach me at: [e-mail]
Instagram: / irtiza.hafiz

[@serbanherlea5755]

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!

[@haneulkk]

It was so easy to understand! Thank you!

[@tianqizhang1573]

Great explanation, easy to understand!

[@10yearsago84]

Really loved the explanation !!

[@letsCherishCoding]

Amazing explanation!!

[@brianpack369]

I am now on course to crash a Cassandra database.

[@alaad1009]

Excellent video man !

[@irtizahafiz]

Glad you liked it!

[@athulraveendran75]

Great explanation ❤

[@motazhejaze38]

many thanks

[@dineshkuruba1880]

great video, please do a video on how the data is stored on disk with different column families

[@irtizahafiz]

Good idea. I will!

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

[@mpaltanwale]

Commitlog is on disk and not in memory, if you want to make correction in the video.

[@irtizahafiz]

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

[@rajesh4361]

@@Khushboo1811 it actually does the bulk update to Disk..every 10seconds if i am not wrong.

[@h.mantri]

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-xx2ef]

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

[@Sverdiyev]

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

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

[@onyedikachioko7174]

Is a distributed database all you need for a system to be distributed?

[@irtizahafiz]

I think you can use the term in this case, yes.

[@Entertainment_Zone2522]

Bro can you please make video on zipkin traces Store in Cassandra database

[@irtizahafiz]

Added to my backlog. Thanks for the idea!

[@catalinim4227]

multiple players with the same name with the same club? ... 😵‍💫what?

[@irtizahafiz]

That analogy fell apart very quickly LOL. But hopefully you get an idea of how the different keys work.