Apache Cassandra may have served you well. But alas, nothing is ever perfect, so you’re looking to migrate from Apache Cassandra to ScyllaDB. Typically sub-millisecond consistency, performance of various operations, compaction, as well as read/write latency (especially under heavy loads) can be less than optimal.
You have probably heard that ScyllaDB is API compatible with Apache Cassandra. Given the 10x performance increase with improved latency, and with zero downtime for the Cassandra migration process, who wouldn’t want to try it out?
How do you actually migrate from Apache Cassandra to ScyllaDB? To help you through the process, we created our Apache Cassandra to ScyllaDB Migration Process documentation.
There are four phases in the Apache Cassandra migration process once you’ve created your Apache Cassandra schemas in ScyllaDB:
- Dual writes: updating application logic to write to both databases:
- Forklifting: migrating historical data (SSTables) from Apache Cassandra to ScyllaDB using sstableloader:
- Dual reads: validating ongoing data sync between the two DBs:
- Phase out: The final phase takes place as the old Apache Cassandra database is phased out. After this point, all reads and writes go via the new ScyllaDB instance.
The detailed steps and timeline can be found in our comprehensive Apache Cassandra to ScyllaDB Migration Process Documentation.
Before you migrate from Apache Cassandra, learn more!
Learn about consistency levels with our console demo. Read about our architecture, and see how easy it is to get started with ScyllaDB. Check out ScyllaDB for administrators, learn ScyllaDB for developers, model your own CQL, browse our FAQ and knowledge base, sharpen up on your technical terminology, and learn how to contribute to ScyllaDB.
You can also see our latest Cassandra vs ScyllaDB performance comparisons in this 2 part blog series: