Migrate from Aerospike to KiviDB

Aerospike and KiviDB both keep records in memory and answer in well under a millisecond, but they are not wire-compatible. Aerospike has its own protocol, clients and data model (namespaces, sets, records and bins); KiviDB speaks the Redis protocol. Moving means two things: copying the records into KiviDB keys, and changing the code that reads and writes them. This guide covers both, with a loader and a verify script you can run as they are.

Everything here was run against Aerospike Database Community Edition 8.1.2 and KiviDB 1.2.0, with the Aerospike Python client 19, Java client 10 and Go client v8 on one side, and redis-py, Jedis and go-redis on the other.