Wrap up

You registered driver_stats and pricing on the driver entity, materialized both into Aerospike, read features from both in one get_online_features call, and confirmed that materializing driver_stats alone updated only its map entries while pricing values on each record stayed the same.

Stop Aerospike

1. Stop and remove the Aerospike container:

   docker rm -f aerospike

Checklist

• I’ve stopped the Aerospike Docker container.

Share

Congratulations on completing this tutorial! Share your achievement with the world and let everyone know about your newly acquired skills.

Next Steps

• Tutorial: Route hot and cold Feast features to memory and flash when memory cost or capacity planning drives namespace tiering.

• Tutorial: Stream fraud velocity features with Feast when features must stay fresh through store.push() on a streaming path.

• Part 3: Model Serving to see feature retrieval in a prediction pipeline.

• Read the Aerospike online store reference for namespace and set overrides, prewriting hooks, and TTL configuration.

• Reproduce cross-store latency with feast-benchmarks.