How omerfeyzioglu/glider works
Glider is a single-node vector database whose acknowledged writes are durable in object storage. The principal workflow is: an API client creates a collection, writes vectors and metadata, then queries nearest neighbors with optional filters; the server routes work through admission to the segmented engine, which publishes durable state and serves results from stored blocks. Distinct capabilities include collection management, optional text embedding, clustered ANN maintenance, crash recovery, and agent memory. Relationships use README statements and visible imports; unsampled implementations are represented only where their subsystem is documented.
Main entry points: segmented.rs Segmented database · http.rs HTTP API · store.rs Object store interface · admission.rs Write admission
Components 24
API and clients
- Python client
clients/python/glider_client/client.py - MCP memory server
clients/python/glider_client/mcp_server.py
Server services
- HTTP API
src/server/http.rs - Collection catalog
src/server/catalog.rs - Multi-collection service
src/server/multi.rs - Text embedding
src/server/embedding.rs
Vector engine
- Write admission
src/admission.rs - Segmented database
src/segmented.rs - Metadata filters
src/filter.rs - Clustered ANN
src/segmented/clustered.rs - Cluster conversion
src/segmented/convert.rs - Block routing sketches
src/segmented/sketch.rs - Segment serving
src/segmented/serving.rs - SSD block cache
src/segmented/cache.rs
Durability and storage
- Retry outcomes
src/retry.rs - Writer lease
src/lease.rs - Recovery
src/recovery.rs - Object store interface
src/store.rs - S3-compatible store
src/store/s3.rs
Operations
- Backup and restore CLI
src/bin/glider-admin.rs
Other components
- API user
- S3-compatible storage
- Embedding provider
- AI agent
Connections 27
- API user → Python client: uses client
README.md - API user → HTTP API: calls API
README.md - Python client → HTTP API: sends requests
README.md - AI agent → MCP memory server: invokes tools
README.md - MCP memory server → Python client: uses client
clients/python/glider_client/mcp_server.py - HTTP API → Collection catalog: serves collections
src/server/mod.rs - HTTP API → Text embedding: routes embedding
src/server/http.rs - Embedding provider → Text embedding: provides vectors
README.md - HTTP API → Write admission: submits work
- Collection catalog → Segmented database: opens collections
src/server/catalog.rs - Multi-collection service → Segmented database: manages collections
- Write admission → Segmented database: commits writes
src/admission.rs - Write admission → Retry outcomes: tracks outcomes
src/admission.rs - Segmented database → Retry outcomes: records outcomes
src/segmented.rs - Segmented database → Object store interface: reads and publishes
src/segmented.rs - Segmented database → Metadata filters: applies filters
- Segmented database → Clustered ANN: routes queries
src/segmented.rs - Segmented database → Cluster conversion: starts conversion
src/segmented/convert.rs - Segmented database → Block routing sketches: routes blocks
src/segmented/sketch.rs - Segmented database → Segment serving: serves queries
src/segmented.rs - Segment serving → SSD block cache: uses cache
- Segmented database → Writer lease: coordinates takeover
src/segmented.rs - Writer lease → Object store interface: fences writer
src/lease.rs - Recovery → Object store interface: replays state
- Object store interface → S3-compatible store: implemented by
src/store.rs - S3-compatible store → S3-compatible storage: reads and writes
src/store/s3.rs - Backup and restore CLI → Object store interface: backs up and restores
README.md