We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

A deep dive and comparison of Python drivers for Cassandra and Scylla

Formal Metadata

Title
A deep dive and comparison of Python drivers for Cassandra and Scylla
Title of Series
Number of Parts
130
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
This talk will explain the thread-per-core data architecture of Scylla and detail how we implemented "shard-awareness" in the Cassandra Python driver which allows to route queries down to the right CPU! Cassandra's and Scylla's architecture and topology rely on the usage of a consistent token ring to distribute their data evenly on the cluster. The cassandra-python driver is used widely to interact with those NoSQL databases. It implements connection pools and token awareness allowing the driver to route queries to the right node based on its knowledge of where the data is. But Scylla goes one step further as it also dedicates CPUs to a smaller portion of the data on each node (called shards). This means that **we can route CQL queries not only to the right node but to the right CPU**! This talk will give implementation details on how we have done it. Talk audience requirements: having a minimal knowledge of what Cassandra and a consistent hash ring are.