05 | Intro to Cassandra - The Art of Data Modeling

preview_player
Показать описание
Welcome to the Intro to Cassandra Crash Course! In this video series, we'll go over the basics of how Apache Cassandra works and get hands on with implementing a basic Cassandra Database in the cloud!

💻 Create your Cassandra Database:

📥 Workshop Materials:

CONNECT WITH DATASTAX

About DataStax:

About DataStax Developer:
Рекомендации по теме
Комментарии
Автор

This content is GOLD. Thank you for your time/effort!

warriorfb
Автор

Coming from the relational world, this video does a great job of explaining the nosql approach

BrianTX
Автор

very good explanation of essence of Kassandra data model! Finally I got it :) Put a like. Thank you!

korshak
Автор

dude, you're amazing man. Props to you.

ethanquenum
Автор

So we would have to write into two tables if the user ever comments on a video? One for the user commented table and the other the video commented table. Would this be the best practice for a n - m relationship alternative for Cassandra @DataStax Developers

DallasCowboyFan
Автор

I'm having trouble understanding whether the commentid columns in this example would contain the same value per-comment. I'm assuming they would be the same, but would that mean that in this example you would generate the commentid before inserting into both of these tables? Or maybe the commentid columns are unique...

natemanafter
Автор

if you know where your star schema center is and how often is going to be modified. denormalization isn't bad.

qrjftvx
Автор

Very well explained but now I'm wondering in this example, say there's a new comment generated from the UI. Would there need to be two inserts now for each table? I could see mismanagement of CRUD getting the data out of whack quite easily. Deleting and editing seem like a nightmare.. not sure if this is answered in your next video... But this is kinda terrifying.

cnotation
Автор

great crash course. not sure why comments are both stored in comments_by_user and comments_by_video tables. seems like data redundant to me, an anti-design pattern. furthermore, if a comment is to be updated the change must be applied to both tables.

glennchoi