ScyllaDB achieves Cassandra feature parity, adds HTAP, cloud, and Kubernetes support
ScyllaDB, the open-source drop-in replacement for Apache Cassandra, is growing up. Version 3.0 closes the gap in terms of features, and has a few extras to add on top of superior performance over Cassandra.
ScyllaDB promises something simple, alluring, and hard to believe: Keep your codebase, replace Cassandra with ScyllaDB, get up to 10-times boost in performance. How can this be? In a nutshell, different implementation language (C++ rather than Java), more low-level programming paradigm (such as memory or socket allocation) via Seastar, and auto-tuning capabilities.
That was the story of ScyllaDB 2.0. There were, however, a few features missing from ScyllaDB in order to be an exact drop-in replacement for Cassandra. Now, with version 3.0 announced in ScyllaDB Summit, ScyllaDB not only closes the gap, but embarks on its own journey, starting out with adding HTAP (Hybrid Transactional – Analytic Processing) capabilities and going cloud.
Let’s start with the features that were once missing from ScyllaDB and are now there. Materialized Views, Secondary Indexes, and File Formats may not sound very sexy, but they can make a lot of difference in application development and performance. Dor Laor, ScyllaDB co-founder and CEO, said they dedicated lots of hard work and a big part of their R&D to reach parity in terms of functionality: