Aerospike

Aerospike is a high-performance distributed database designed for sub-millisecond latency at scale — used by Snap, Wayfair, PayPal, and major ad-tech platforms for real-time data access. Its hybrid memory architecture (indexes in RAM, data on SSD) delivers consistent performance at large data volumes. For agents, Aerospike is relevant when cache/data requirements demand predictable sub-ms latency at scale beyond what Redis can offer, or when data volumes exceed Redis's in-memory capacity constraints. REST Gateway enables HTTP access; native clients provide the best performance. Aerospike Cloud is the managed offering. Confidence is docs-derived.

REST Gateway at {host}:8080. Resources: records (key-value), namespaces, sets, secondary indexes. GET /v1/kvs/{namespace}/{setName}/{userKey} reads a record by primary key. POST /v1/kvs/{namespace}/{setName}/{userKey} writes a record (JSON bins). DELETE /v1/kvs/{namespace}/{setName}/{userKey} deletes. PUT /v1/kvs/{namespace}/{setName}/{userKey} updates specific bins. Query via POST /v1/execute/sql (Aerospike SQL GA). Native AerospikeClient (Java/Python/Go) preferred for full feature access: batch operations, CDT (collection data types), geospatial queries, UDFs. REST Gateway is a convenient entry point but adds latency vs. native client.

Aerospike supports multiple security modes: no auth (development), password auth (username + password per user), LDAP, and TLS with client certificates. Aerospike Cloud uses role-based access with user management via Cloud Console. REST Gateway auth configured via gateway config file (username/password or token). RBAC at namespace and set level. TLS mutual auth available for enterprise deployments. Aerospike Cloud enforces TLS; self-hosted security depends on configuration.

Operations return HTTP 200/400/404/500. Record not found returns 404. Write conflict (generation mismatch for optimistic locking) returns 409. REST Gateway timeout returns 503. Native clients handle cluster topology automatically; failed node operations are retried on healthy nodes. Aerospike's smart client maintains the cluster partition map, routing requests to the correct node directly. Aerospike Cloud SLA: 99.95%. Self-hosted single-node vs. multi-node cluster reliability varies significantly.

docs.aerospike.com provides comprehensive documentation: data model concepts (namespaces, sets, records, bins), REST Gateway API reference, client library guides for all supported languages, Aerospike SQL documentation, secondary index guide, and Aerospike Cloud setup. Documentation quality is high and technically detailed. Getting started is fast with Aerospike Cloud (free tier) or Docker Community Edition. Aerospike University provides free online courses. Commercial support via Aerospike.