Aerospike key-value store (KVS) operations associate keys with a set of named values. On cluster startup, Aerospike configures policy containers—namespaces (RDBMS databases)—which control the retention and reliability requirements for a set of data. Namespaces are divided into sets (RDBMS tables) and records (RDBMS rows). Each record has a unique indexed key, and one or more bins (RDBMS columns) that contain the record values. Aerospike supports numerous data types used for bin values, as arguments, and as UDF return values. Aerospike allows value-based queries using secondary indexes, where string and integer bin values are indexed and searched using equality (string or numeric) or range (numeric) filters. User-Defined Functions (UDFs) extend the functionality and performance capabilities of the Aerospike Database engine. In Aerospike, the aggregations framework allows fast, flexible query operations. Similar to MapReduce systems, aggregation emits results in a highly parallel fashion. Aerospike supports large data types (LDTs) that allow individual record bins to efficiently store large collections of elements. In Aeropike, you can use list data types when dealing with a size-bound list residing in a single bin. List operations allow server manipulation (such as adding or removing an item) without having to read and replace the entire bin value. Aerospike supports Geospatial store, index, and query.

* The library works within a fixed amount of memory. No garbage collector. Small metadata, near perfect memory utilization (overhead is 5-7% of the total memory). * Besides memory management, Cachelot ensures smooth responsiveness, without any "gaps" for both read and write operations. * Cachelot can work as a consistent cache, returning an error when out of memory or evicting old items to free space for new ones. * The code is written in C++ and it is highly optimized. You can use cachelot on platforms with limited resources, like IoT devices or handheld.