Amazing video talking about a lot of features that cassandra provides. but it didn't talk about the wide column oriented feature !! Can anyone explain about the wide column store ? when to use it and all ?
The Katacoda course is no longer available. Can you please guide me to a course where I can run the queries and get hands on experience like Katacoda offered
I have a quick question, earlier you mentioned that each partition gets map to a specific node (consistent hashing) and then it gets replicated based on RF factor. But then , later you said that any node can receive request and then will redirect to the right set of nodes?
Basically the coordinator node is just there to receive the request and forward it to the ones that will actually store it. They do not store the data themselves (unless the data happens to fall under one of their assigned partition ranges).
You explained this clearer than anyone at my job who has years of experience. It's a skill and art that not everyone has - the ability to teach.
as for now, the katacoda site isnt up ...where else i can dive more deeper to study cassandra?
Really informative and describe in an easy to understand manner, thank u so much.
You really explained that well!!!
Amazing video talking about a lot of features that cassandra provides.
but it didn't talk about the wide column oriented feature !!
Can anyone explain about the wide column store ? when to use it and all ?
Thanks for the information . Amazing way to explain it!
that's what i was looking for, thanks a lot
The Katacoda course is no longer available. Can you please guide me to a course where I can run the queries and get hands on experience like Katacoda offered
We are working on a customer solution but for now you can go to killercoda.com/datastaxdevs/
I have a quick question, earlier you mentioned that each partition gets map to a specific node (consistent hashing) and then it gets replicated based on RF factor. But then , later you said that any node can receive request and then will redirect to the right set of nodes?
Basically the coordinator node is just there to receive the request and forward it to the ones that will actually store it. They do not store the data themselves (unless the data happens to fall under one of their assigned partition ranges).
this is a really good video, well done
Just to the point , awesome video
Amazing! Great content!
478 likes vs 307 dislikes. I wonder why people disliked the video considering there are no negative comments.
Edit: probably the inconsistent audio.
1:25 or so I could hear a baby crying out in the background 🤷♂️ I didn't do a thumbs down though.
Excellent. Just wow!
Very concise and packs key information 👍
Glad you think so! 🍻 - Erick Ramirez
Amazing video, thanks!
DynamoDb aka AWS managed Cassandra finally making sense now, thanks.
The service the closest to Cassandra in AWS is AWS keyspaces. DynamoDB is totally a different technology.
This is very well done.
great work
Because casandra accounts for so much redundancy isnt it slow.
It is not. It is superfast for both reads/writes and can handle internet scale which is why tech giants use it. 👍 [Erick Ramirez]
Are there kids crying in the background? I kept pausing thinking my kids were awake.
Yes. (I was the kid)
did the same thing... though I was losing my mind
ajayib