Contentserv, a leader in Product Information Management (PIM) systems, needed to continue to scale and accelerate. They wanted to achieve a migration from Cassandra to Scylla with zero code or data changes. Discover the methods they used to achieve a seamless migration.

1. Our Journey from
Cassandra to Scylla
Pankaj Gajjar

2. Pankaj Gajjar
Enterprise Architect (TOGAF Certified),
Contentserv.
■ 14+ years experience in product development (architecture,design & implementation)
■ 11+ years at Contentserv
■ Apart from Enterprise Architect role with Contentserv, I've been a Speaker,
Technical Reviewer & Mentor in different IT communities
2

3. Topics
▪ Contentserv overview
▪ Use case: PIM (Product Information Management)
▪ Why we chose Scylla
▪ How we migrated data from Cassandra to Scylla
▪ Challenges
3

4. Contentserv Overview
■ Leader in the Forrester Wave™ for Product Information
Management (PIM) solutions
■ Futurize your customers’ product experience (PXP)
● PIM – Product Information Management
● MDM – Master Data Management
● MXM – Marketing Experience Management
4

5. Use Case: Product
Information Management
■ PIM – Product Information Management Collect product
information from multiple sources and lay the foundation
for powerful, multichannel product communication.
■ Using Contentserv, you can deliver outstanding product
experiences that meet and exceed customer expectations.
5

6. ■ Contentserv able to export data via Channel concept.
■ The Channel is endpoint to deliver the content to end user.
■ Require faster read to get complete content.
■ Scylla’s NoSQL wide-column database fits well as per the
architecture design.
6
Use Case: Product
Information Management

7. Why We Chose Scylla
■ We already placed the Cassandra 3.11.x
■ Looking for 100% compatible alternative to Cassandra
■ Minimal or zero code change at application level
■ Zero change in data model at database level
■ Worked well with fewer resources than Cassandra setup
■ We chose Scylla 4.x
7

8. Data Migration
Two recommended strategies:
■ Dual Write: Application logic is updated to write to both DBs.
■ Forklifting: Migrate historical data from Apache Cassandra
SSTables to Scylla.
8

9. ■ We chose the snapshot strategy.
● Take schema backup from Cassandra node.
cqlsh -e DESC SCHEMA > cas_node1.cql
● Take snapshot backup
nodetool snapshot keyspace_name
● Restore it (schema & snapshot) at Scylla node.
9
Data Migration

10. Challenges
■ Use sstable_compression: 'org.apache.cassandra.io.compress.LZ4Compressor'
■ Not support of SASI Index - org.apache.cassandra.index.sasi.SASIIndex
■ This limit places a bound on the size of IN tuples, especially
when multiple clustering key columns have IN restrictions.
Increasing this value can result in server instability.
■ Adjust params in yml file
● max_clustering_key_restrictions_per_query
● Max_partition_key_restrictions_per_query
■ To SIGHUP - sudo pkill -x -HUP scylla
10

11. Thank You
@javaamtho
pankajgajjar@gmail.com
Pankaj Gajjar
11

12. Download Scylla Open Source:
scylladb.com/download
Talk to an expert:
scylladb.com/consultation
Take a test drive:
scylladb.com/test-drive
Experience Scylla for Yourself
12