ScyllaDB Open Source has a rich set of new production-ready features, including Lightweight Transactions (LWT), DynamoDB API compatibility, Change Data Capture, offline installers and more. Already the best high-performance NoSQL database for big data workloads, ScyllaDB was built to replace Apache Cassandra and Amazon DynamoDB by taking their best attributes and improving on performance, scalability, and cost-efficiency.
ScyllaDB now supports the new AWS EC2 I4i series instances. The I4i series provides superior performance over the I3 series due to a number of factors: the Intel Xeon Ice Lake processors, the AWS Nitro System and low-latency Nitro NVMe SSDs. ScyllaDB can achieve 2x throughput and lower latencies on I4i instances over comparable i3 servers.
Reverse queries are SELECT statements that use reverse order from the table schema. If no order was defined, the default order is ascending (ASC). For example, imagine rows in a partition sorted by time in ascending order. A reverse query would sort rows in descending order, with the newest rows first. Reverse queries were improved in ScyllaDB Open Source 4.6, and are further improved in 5.0, first, to return short pages to limit memory consumption, and secondly, for reverse queries to leverage ScyllaDB’s row-based cache (before 5.0 they bypassed the cache).
A new system.config virtual table allows querying and updating a subset of configuration parameters over CQL. These updates are not persistent, and will return to the scylla.yaml update after restart. Nodetool command information can also be accessed via virtual tables, including snapshots, protocol servers, runtime info, and a virtual table replacement for nodetool versions. Virtual tables allow remote access over CQL, including for Scylla Cloud users.
Unstable schema management has been a problem in all Apache Cassandra and ScyllaDB versions so far. Using the new Raft consensus protocol support in ScyllaDB, you can now perform immediate and safe schema management for DDL operations like CREATE, ALTER, DROP for KEYSPACE, TABLE, INDEX, UDT, MV etc.
Tombstones (markers that indicate deleted records) that are older than the most recent repair can now be automatically purged, and newer ones will be kept. This drops tombstones more frequently if repairs are made in a timely manner, and prevents data resurrection if repairs are delayed beyond gc_grace_seconds.
Get started on the path to ScyllaDB expertise
It’s easy to get started with our NoSQL DBaaS