We will walk through how Discord rebuilt its message storage layer from the ground up. We will learn the issues Discord faced with Apache Cassandra® and their shift to ScyllaDB.
I'd be curious to hear Discord's comments on Scylla's new licensing structure. Also, it's been a long time since I've heard of anyone having GC issues with Apache Cassandra. G1GC helped a lot with that, and the collectors available in the more recent JDKs (ZGC, Shenandoah) make it even more of a non-issue.
ScyllaDB will release a benchmark with Cassandra 5.0.
ZGC and new JVMs definetly makes things much better. We noted that in our Cassandra 4.0 benchmark. However, a well crafted C++ code base will always behave better than Java. You're doing an upheap battle.
ScyllaDB made lots of progress in features, Raft and fencing for example. There are multiple drives to replace Cassandra, even when it comes free
This is such a well written article about practical considerations for large scale distributed systems. Valuable insight, thanks for sharing.
I'd be curious to hear Discord's comments on Scylla's new licensing structure. Also, it's been a long time since I've heard of anyone having GC issues with Apache Cassandra. G1GC helped a lot with that, and the collectors available in the more recent JDKs (ZGC, Shenandoah) make it even more of a non-issue.
ScyllaDB will release a benchmark with Cassandra 5.0.
ZGC and new JVMs definetly makes things much better. We noted that in our Cassandra 4.0 benchmark. However, a well crafted C++ code base will always behave better than Java. You're doing an upheap battle.
ScyllaDB made lots of progress in features, Raft and fencing for example. There are multiple drives to replace Cassandra, even when it comes free
Hello
Ok
nice