liveBook · Manning

Qdrant

As explained in Spring AI in Action

Qdrant is a vector database for storing, filtering, and similarity-searching vector data and its associated payloads.

Qdrant is a vector store for keeping document embeddings and retrieving documents similar to a question. Spring AI provides a common abstraction, so changing vector stores has little effect on application development. section 4.2 section 4.4

A practical setup runs Qdrant with Docker Compose. Expose ports 6333 and 6334, start the service, and configure Spring AI to use the local instance. section 4.2

services:
  qdrant:
    image: 'qdrant/qdrant:latest'
    ports:
      - '6334:6334'
      - '6333:6333'

Use this Compose definition to start Qdrant and expose the HTTP and client ports used by the application. section 4.2

A document pipeline can use Qdrant to:

  • Store chunks produced from game-rule documents. section 4.3.4
  • Organize stored chunks in a named collection; Qdrant calls individual chunks points. section 4.3.4
  • Support RAG by retrieving documents similar to a question and supplying them as prompt context. section 4.4

Verify an ingested collection

After loading Burger Battle rules, query Qdrant’s collections endpoint and count points in board-game-buddy. The example reports one collection containing two points.

How Spring AI in Action covers it

How deep it goes
Covers Docker setup, collection verification, point counting, and RAG integration, while deferring similarity mathematics to the vector store.
Examples
Uses game-rule documents, the board-game-buddy collection, Burger Battle, HTTPie requests, and a two-point count.
What it assumes
Assumes Docker installation and basic Spring Boot build configuration, while hiding embedding and cosine-distance calculations behind libraries.
What you can do after
Operate/configure Qdrant with Docker Compose, verify stored points through its HTTP API, and connect it to Spring AI RAG.
How it connects
Connects vector stores, embeddings, document chunking, Docker Compose, Spring AI, HTTP APIs, and retrieval-augmented generation.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spring AI in Action. The section links point to the parts of the book it draws on.