Databases

My database expertise encompasses the design of relational databases using DBML for versatile script generation across different database vendors and comprehensive documentation, coupled with foundational SQL skills for initial database seeding and the principles of columnar databases.

The work that keeps me closest to databases now is AI retrieval, and it runs on four stores. In MCP Context Server, the source-available memory layer for LLM agents I build and publish, I designed both storage backends — SQLite (WAL mode, the zero-configuration default) and PostgreSQL (MVCC, asyncpg pooling, JSONB indexing for high-concurrency deployments) — together with their vector extensions, sqlite-vec and pgvector, down to the dimension cap pgvector's HNSW index puts on uncompressed vectors and the storage-compression trade-off that works around it. In AIR API, the retrieval platform I built at Spotware, that job is split: Chroma holds the vectors behind a fully asynchronous wrapper I wrote over the LangChain client, MongoDB holds the parent documents behind an async store of my own, and PostgreSQL backs the ingestion record manager that tracks what has already been indexed. On top of storage sits the retrieval layer: full-text indexes (SQLite FTS5, PostgreSQL tsvector) ranked with BM25 or ts_rank, embeddings ranked by vector distance, the two fused with Reciprocal Rank Fusion — which I wrote from scratch in MCP Context Server and extended in AIR API to fuse several query formulations in one pass — and a cross-encoder reranker sharpening whatever survives the fusion. This diverse experience ensures robust and scalable data architecture solutions for complex analytical and operational requirements.