How teams scaled ScyllaDB: 2 real case studies
2 of the 73 engineering write-ups in our database mention ScyllaDB in their stack. They come from 1 company (Discord) and were published between 2023 and 2026. It's often paired with Rust (2). 2 of the 2 state concrete scale numbers, for example "dozens of clusters, hundreds of database nodes" (Discord). Each card below links to our short summary and the original post.
How Discord Automates ScyllaDB Clusters at Scale
Discord's 7-person persistence team replaced fragile Python and bash scripts with the Scylla Control Plane, a Rust framework of idempotent tasks with declared preconditions, composed into YAML workflows. Jobs batch nodes by availability zone with concurrency limits to protect quorum, store their state in SQLite so they resume after interruptions, and send a webhook alert on unrecoverable errors. Operations like standing up shadow clusters and rolling upgrades went from a day and a half of babysitting to under two hours.
How Discord Stores Trillions of Messages
Discord moved its message store from Cassandra to ScyllaDB and put Rust data services in front of it to coalesce hot-partition requests.