Module: Pikuri::VectorDb::Server
- Defined in:
- lib/pikuri/vector_db/server.rb,
lib/pikuri/vector_db/server/chroma.rb,
lib/pikuri/vector_db/server/qdrant.rb,
lib/pikuri/vector_db/server/in_memory.rb,
lib/pikuri/vector_db/server/docker_container.rb
Overview
Namespace for the vector-database supervisors — one per Backend engine,
named to pair (Backend::Qdrant ↔ Qdrant, etc.). The backend
owns the store protocol; the server owns its lifetime. All three
implement the same duck-typed protocol (+.ensure_running+ /
#ensure_running! / #client(collection:) / #close), so a host chains
ensure_running.client(...) and closes at teardown without branching per
engine.
For Qdrant / Chroma the lifetime is a docker container, both composing the shared DockerContainer helper so each supervisor is just the engine's identity. InMemory is the null supervisor (no process, just the in-process store registry). Hosts already running an engine construct the backend directly and never touch this namespace.
Only supervisors (and DockerContainer) live here. Classes with "server" in the name that are actually HTTP clients — Reranker::LlamaServer, Tokenizer::LlamaServer — stay in their feature namespaces.
Defined Under Namespace
Classes: Chroma, DockerContainer, InMemory, Qdrant