I'd much rather use OSS like Aerospike or ScyllaDB for this workload and still retain some agency over my deployment.

Getting a system like this right is super hard, and not being OSS, you are at the mercy of the cloud provider to fix issues.

Aerospike recently released their own Redis protocol proxy for Redis [1]. Scylla has their own nascent Redis api driver [2], would love to get folks feedback on it.

[1] https://github.com/aerospike/skyhook

[2] https://siddharthc.medium.com/redis-on-nvme-with-scylladb-5e...

I'm really impressed with Seastar [1], the library ScyllaDB wrote to solve for writing non-blocking, asynchronous code in C++. It's also used by Redpanda [2], a Kafka-compatible service in the same vein as MemoryDB/Skyhook.

[1] https://github.com/scylladb/seastar

[2] https://github.com/vectorizedio/redpanda

The arch of ScyllaDB blew my mind gotta say. Great talk [1] by Avi Kivity, co-founder of Scylla that goes over the design and architecture.

Glommio [2] (believe it used to be called Scipio) is a thread-per-core framework for Rust modeled after Seastar.

There isn't much in the hn hive mind about it, this one [3] stands out.

[1] https://www.youtube.com/watch?v=0S6i9BmuF8U

[2] https://github.com/DataDog/glommio

[3] https://news.ycombinator.com/item?id=24976533