Join the global Cassandra community on April 28 as we celebrate the upcoming launch of the 4.0 release!
Masterless architecture and low latency means Cassandra will withstand an entire data center outage with no data loss—across public or private clouds and on-premises.
Cassandra's support for replicating across multiple datacenters is best-in-class, providing lower latency for your users and the peace of mind of knowing that you can survive regional outages. Failed nodes can be replaced with no downtime.
To ensure reliability and stability, Cassandra is tested on clusters as large as 1,000 nodes and with hundreds of real world use cases and schemas tested with replay, fuzz, property-based, fault-injection, and performance tests.
Cassandra consistently outperforms popular NoSQL alternatives in benchmarks and real applications, primarily because of fundamental architectural choices.
Choose between synchronous or asynchronous replication for each update. Highly available asynchronous operations are optimized with features like Hinted Handoff and Read Repair.
The audit logging feature for operators tracks the DML, DDL, and DCL activity with minimal impact to normal workload performance, while the fqltool allows the capture and replay of production workloads for analysis.
Cassandra is suitable for applications that can't afford to lose data, even when an entire data center goes down. There are no single points of failure. There are no network bottlenecks. Every node in the cluster is identical.
Read and write throughput both increase linearly as new machines are added, with no downtime or interruption to applications.
Cassandra streams data between nodes during scaling operations such as adding a new node or datacenter during peak traffic times. Zero Copy Streaming makes this up to 5x faster without vnodes for a more elastic architecture particularly in cloud and Kubernetes environments.
Cassandra is used by thousands of companies with large active data sets.
Since 2016, application engineers at Bloomberg have turned to Cassandra because it’s easy to use, easy to scale, and always available. We serve up more than 20 billion requests per day on a nearly 1 PB dataset across a fleet of 1,700+ Cassandra nodes. – Isaac Reath, Software Engineering Team Lead, NoSQL Infrastructure at Bloomberg
Here’s what the Cassandra community has been doing to advance the world’s premier open source NoSQL database.
Improving Apache Cassandra’s Front Door and Backpressure
As part of CASSANDRA-15013, we have improved Cassandra’s ability to handle high throughput workloads, while having enough safeguards in place to protect itself from potentially going out of memory. In order to better explain the change we have made, let us understand at a high level, on how an incoming request is processed by Cassandra before the fix, followed by what we changed, and the new relevant configuration knobs available.Read More
Cassandra Changelog Blog #6
The Cassandra Changelog blog is our monthly roundup of key activities and knowledge to keep the community informed. This month includes an update on the 4.0 rc-1 release, welcoming a new committer, the Cassandra World Party, Google Summer of Code (GSoC), and more.Read More
Cassandra Kubernetes SIG March Meeting
Recent updates to the community-based operator by the Kubernetes SIG have seen the specification for seeds now supporting hostnames and separate seeds for separate data centers. Currently, the SIG is discussing whether cass-operator should have CRDs for keyspaces and roles, how to accomplish pod-specific configurations, and whether CRDs should represent Schema.Watch Recording