feast-dev · vkagamlyk · Apr 20, 2026 · Apr 20, 2026 · Apr 20, 2026 · Apr 20, 2026
diff --git a/.secrets.baseline b/.secrets.baseline
@@ -957,7 +957,7 @@
         "filename": "infra/feast-operator/api/v1/featurestore_types.go",
         "hashed_secret": "44e17306b837162269a410204daaa5ecee4ec22c",
         "is_verified": false,
-        "line_number": 906
+        "line_number": 907
       }
     ],
     "infra/feast-operator/api/v1/zz_generated.deepcopy.go": [
@@ -989,7 +989,7 @@
         "filename": "infra/feast-operator/api/v1alpha1/featurestore_types.go",
         "hashed_secret": "44e17306b837162269a410204daaa5ecee4ec22c",
         "is_verified": false,
-        "line_number": 649
+        "line_number": 650
       }
     ],
     "infra/feast-operator/api/v1alpha1/zz_generated.deepcopy.go": [
@@ -1555,5 +1555,5 @@
       }
     ]
   },
-  "generated_at": "2026-06-11T15:45:28Z"
+  "generated_at": "2026-06-16T21:53:17Z"
 }
diff --git a/README.md b/README.md
@@ -227,6 +227,7 @@ The list below contains the functionality that contributors are planning to deve
   * [x] [SingleStore](https://docs.feast.dev/reference/online-stores/singlestore)
   * [x] [Couchbase](https://docs.feast.dev/reference/online-stores/couchbase)
   * [x] [MongoDB](https://docs.feast.dev/reference/online-stores/mongodb)
+  * [x] [Aerospike](https://docs.feast.dev/reference/online-stores/aerospike)
   * [x] [Qdrant (vector store)](https://docs.feast.dev/reference/online-stores/qdrant)
   * [x] [Milvus (vector store)](https://docs.feast.dev/reference/online-stores/milvus)
   * [x] [Faiss (vector store)](https://docs.feast.dev/reference/online-stores/faiss)

@@ -164,6 +164,7 @@
   * [SingleStore](reference/online-stores/singlestore.md)
   * [Milvus](reference/online-stores/milvus.md)
   * [MongoDB](reference/online-stores/mongodb.md)
+  * [Aerospike](reference/online-stores/aerospike.md)
   * [Elasticsearch](reference/online-stores/elasticsearch.md)
   * [Qdrant](reference/online-stores/qdrant.md)
   * [Faiss](reference/online-stores/faiss.md)

@@ -278,6 +278,7 @@ The online store is the single largest factor in `get_online_features()` latency
 | **DynamoDB** | 2–5 ms | Yes | Serverless, auto-scaling on AWS | Pay-per-request cost; batch API limits (100 items) |
 | **PostgreSQL** | 3–10 ms | No (threadpool) | Teams with existing Postgres infra | Connection pooling needed at scale |
 | **MongoDB** | 2–5 ms | Yes | Flexible schema, async-native | Requires index tuning for large datasets |
+| **Aerospike** | < 1 ms | No (threadpool) | Ultra-low latency, hybrid memory (RAM + SSD), large datasets | Namespace must be pre-configured on the cluster |
 | **Bigtable** | 3–8 ms | No (threadpool) | Large-scale GCP workloads | Row-key design affects read performance |
 | **Cassandra / ScyllaDB** | 2–5 ms | No (threadpool) | Multi-region, write-heavy | Tunable consistency; requires DC-aware routing |
 | **Remote** | Varies | No (threadpool) | Centralized feature server architecture | Adds an HTTP hop; tune connection pool |
@@ -305,6 +306,7 @@ The feature server can read from the online store using either an **async** or *
 | **MongoDB** | Yes | Yes | Uses `motor` (async MongoDB driver) |
 | **PostgreSQL** | Implemented | No | Has `online_read_async` but does not yet advertise via `async_supported`; uses sync/threadpool path |
 | **Redis** | Implemented | **Yes** | `online_read_async` and `online_write_batch_async` both implemented; uses sync/threadpool path for `get_online_features` (overridden with batched single pipeline) |
+| **Aerospike** | Implemented | No | Async methods wrap the blocking C client via `run_in_executor`; does not yet advertise via `async_supported`, so the server still uses the threadpool path |
 | All others | No | No | Fall back to sync with `run_in_threadpool()` |
 
 **When async matters most:**
@@ -467,6 +469,34 @@ online_store:
 - **`connectTimeoutMS` / `socketTimeoutMS`**: Tighter timeouts improve p99 by failing fast on slow connections.
 - MongoDB is one of the stores with **full async support** (read and write), so it benefits from concurrent feature view reads via `asyncio.gather()`.
 
+### Aerospike tuning
+
+Aerospike offers sub-millisecond reads thanks to its hybrid-memory architecture (primary index in RAM, data on SSD or RAM). Tune the per-call policies in the Feast config and rely on the Aerospike cluster's own tuning for everything else:
+
+```yaml
+online_store:
+  type: aerospike
+  hosts:
+    - ["aerospike-1.internal", 3000]
+    - ["aerospike-2.internal", 3000]
+  namespace: feast
+  read_timeout_ms: 150           # hard deadline for a single-record get
+  write_timeout_ms: 300           # hard deadline for a single-record put/operate
+  batch_total_timeout_ms: 500     # hard deadline for online_read / online_write_batch
+  socket_timeout_ms: 50           # per-attempt deadline so max_retries can actually fire
+  max_retries: 2
+  ttl_seconds: 86400              # record-level TTL; omit to use the namespace default
+  client_kwargs:                  # escape hatch for any client-config field not surfaced above
+    policies:
+      batch:
+        concurrent_nodes: 0       # 0 = parallel to every node (lowest latency on multi-node clusters)
+```
+
+- **`*_timeout_ms` (total)** vs **`socket_timeout_ms` (per-attempt)**: `*_timeout_ms` is the hard deadline for a whole call *including* retries; `socket_timeout_ms` is the per-attempt deadline that allows `max_retries` to actually fire within that budget. Without `socket_timeout_ms`, a single slow attempt can consume the entire total deadline and retries never run.
+- **`hosts`**: List every seed node. The Aerospike client discovers the rest of the cluster automatically and opens one connection pool per node.
+- **`ttl_seconds: 0`** means "never expire"; omit the key to inherit the namespace's `default-ttl`. Expiry is enforced by the server's `nsup` thread — nothing to delete on the client side.
+- Co-locate the feature server in the **same availability zone / rack** as the Aerospike cluster; sub-millisecond reads are bandwidth- and RTT-sensitive.
+
 ### Remote online store tuning
 
 The Remote online store connects to a Feast feature server over HTTP. Connection pooling is critical:
@@ -700,6 +730,7 @@ This applies to every connection-oriented online store:
 | **DynamoDB** | `max_pool_connections` (HTTP pool) | 10 | No hard limit, but AWS SDK has per-process pool caps; monitor throttling |
 | **Redis** | Connection per worker | 1 | `maxclients` on the Redis server (default: 10,000) |
 | **MongoDB** | `maxPoolSize` (in `client_kwargs`) | 100 | Server's `net.maxIncomingConnections` |
+| **Aerospike** | Driver manages pool per seed node | Auto | `proto-fd-max` (default 15000) on each Aerospike node |
 | **Cassandra** | Driver manages pool per node | Auto | `native_transport_max_threads` on each Cassandra node |
 | **Remote** | `connection_pool_size` (HTTP pool) | 50 | The target feature server's worker capacity |
 

@@ -58,6 +58,10 @@ Please see [Online Store](../../getting-started/components/online-store.md) for
 [mongodb.md](mongodb.md)
 {% endcontent-ref %}
 
+{% content-ref url="aerospike.md" %}
+[aerospike.md](aerospike.md)
+{% endcontent-ref %}
+
 {% content-ref url="hazelcast.md" %}
 [hazelcast.md](hazelcast.md)
 {% endcontent-ref %}