Aerospike VS skyhook

Aerospike is a high performance, distributed, scalable, key value database. Aerospike leverages SSD technology to achieve levels of throughput and low latency exceeding even those obtained with in memory products. This allows hardware costs to be reduced 10x or more and data density to be increased 10x or more versus any other high performance solution.

Aerospike is a highly available and scalable NoSQL distributed database used in production to provide blazingly fast performance at Petabyte scale. Production deployments of Aerospike are almost always serving their data from NVMe drives, though it’s possible to run namespaces in memory.

Click the Try Now button in the upper-right corner of aerospike.com, enter your contact information and select the Enterprise Edition option.

Vault 1.7.0 is released, and it includes my contribution to support the Aerospike database as backend storage. See the release notes for more details.

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

Aerospike recently released their own Redis protocol proxy for Redis [1].

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

Migrating to a different technology is always a challenging process. You need to train engineers, rewrite the codebase, and set up a production cluster to take over. Using Skyhook, you can move applications to Aerospike first, then come back to rewrite them as Aerospike native, or if you’re satisfied with their performance, keep them as they are. Or maybe you’re looking to expose your Aerospike data to external Redis-based applications? We would love to hear how you would use this project.