We do and we‘re still okay with it. It‘s an incredible piece of engineering of a database, all optimized towards a single use case: Guaranteed single-milliseco

We do and we‘re still okay with it. It‘s an incredible piece of engineering of a database, all optimized towards a single use case: Guaranteed single-millisecond reads and writes on a key-value store that‘s too expensive to fit in RAM. That being said, nowadays it‘s hard to have a dataset with exactly these properties, and honestly they messed up all other use cases pretty hard. Secondary indices are hard in practice, and so is any other structure, like sorted sets, or lists, or trees, or any kinds of analytics. They tried a lot of things (LDT) and abandoned them again. Also, AS can be a diva at operations. The amount of brains and engineering within Aerospike is mindblowing, but it‘s like a F1 car: The fastest you can build, but everything is special and custom made and expensive to replace. We‘re looking currently at Scylla, which is still decent at K/V (also thanks to recent hardware improvements), but wayyy more flexible from the data model side.