Why Discord is switching from Go to Rust (2020)

Re:Why Discord is switching from Go to Rust (2020) by fiddlerwoaroof on Monday February 22, 2021 @02:16PM (#26229077)

The question I’d have is “why use a custom cache at all”, this sounds like a problem that has a whole pile of battle-tested off-the-shelf solutions.

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust (2020) by jhgg on Monday February 22, 2021 @02:51PM (#26229629)

The original implementation of this "service" was in Redis using lua scripts.

We hit the performance ceiling of redis, and rather than deciding to go with redis-cluster, and dealing with the headache of managing persistent redis, we went this way, so we could consolidate data storage to scylladb/cassandra (it was cassandra at the time of rewrite, scylla now since we've migrated our data stores over).

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust (2020) by muzaffarpur on Monday February 22, 2021 @06:15PM (#26231962)

any reason to not consider Aerospike for Cache?

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust (2020) by jhgg on Monday February 22, 2021 @07:11PM (#26232361)

We don't have any operational experience with Aerospike.

We have a bunch of operational experience with C*/ScyllaDB.

[ Parent | on HN ]