changing Vnode impact on Cluster --> https://thelastpickle.com/blog/2021/01/29/impacts-of-changing-the-number-of-vnodes.html
ER diagram shapes --> https://www.geeksforgeeks.org/introduction-of-er-model/
https://www.edureka.co/blog/interview-questions/cassandra-interview-questions/
I am getting difficulty in understanding vnode cluster concept . Then i watched https://www.youtube.com/watch?v=xhclDLmhdrc&list=PLtZafdfRI4M5blB0jpYtlg70l-W4xVQnO&index=10&t=903s video twice . Now only the concept of vNode is bit clear.
Query First approach
Cassandra gets a lot of its speed in database reads and writes from the fact that it never has to perform any joins on the database in fact in Cassandra it’s impossible to perform joins, so instead of taking a relational model approach we take a query first approach, this means we design our tables for a specific query, as a result, we want to have every table which is catered for a specific query, rather than flexible tables such as this employee table and the company car table, hence, we only ever have to query one table when we’re reading or writing data, obviously there are some consequences to this approach, as we might end up writing the same data to multiple tables just to satisfy different queries but it’s ideal for a Cassandra’s distributed architecture.
No comments:
Post a Comment