Skip to content

Wrap up

For the complete documentation index see: llms.txt

All documentation pages available in markdown.

You connected a FastAPI retail application to Aerospike Database, implemented the data-access layer with the Python SDK, and used Voyager to inspect and edit live records.

Outcomes

You now have a fully working retail application backed by Aerospike. Specifically:

  • store_product, get_product, query, advanced_search, get_cart, and add_to_cart are all implemented against the live cluster.
  • The add_to_cart flow uses a check-and-set update against a nested map document to make concurrent updates safe.
  • You can browse, filter, and edit the underlying data in Voyager.

If you want to compare your implementation to a reference, look at the key_value_service_new_client_answers.py module in the sample repository.

Clean up

Stop the FastAPI application and the Aerospike Database container so they do not occupy ports 8080 and 3000 to 3003 after you finish.

  1. In the terminal that is running the FastAPI application, press Ctrl+C to stop the server.

  2. From the aerospike-client-sdk-workshop repository root, stop and remove the Aerospike container.

    Terminal window
    docker compose down
    [+] Running 2/2
     ✔ Container aerospike-workshop                  Removed
     ✔ Network aerospike-client-sdk-workshop_default Removed
    Example response

    This command stops and removes the aerospike-workshop container and its network. The named volume aerospike-client-sdk-workshop_aerospike-data remains, so the records you wrote in this tutorial are still present the next time you run docker compose up -d.

  3. (Optional) Delete the data volume to start fresh next time.

    Terminal window
    docker compose down --volumes

  4. (Optional) Disconnect Voyager from the local cluster, or remove the cluster entry, so it does not try to reconnect when you next launch Voyager.