Platform · 2023–now · AI Present
Postgres + pgvector
Embeddings back in the database you already run. The default for mid-market RAG — not the quiet alternative.
pgvector stuck because most RAG workloads never needed a new operational surface — they needed an extension, good indexes, and fewer vendors. Specialized vector stores remain for extreme scale; the mutation killed the "you must buy Pinecone" default for mid-market apps. Boring SQL won again.
Context
Demos consolidate; evals remain
AI pair programming changed how code is typed faster than how it is reviewed. Agent frameworks and standalone vector stores sorted into demos versus durable plumbing; mid-market RAG folded back into Postgres. The permanent layer is familiar: evals that gate deploys, model routing for cost, tool protocols instead of plugin snowflakes, and humans who own production. Autopilot rewrites and vibe-shipped auth middleware are still big-bang migrations with better slides — and a longer on-call.
Compare with
Related
Platform · 2022–now
Vector DB gold rush
Specialized embedding stores sold as the default. Mid-market folded back into Postgres — after the vendor tour.
Platform · 1974–now
SQL / Relational
Declarative data that outlived every ORM fashion cycle. Postgres and friends keep winning by being boring.
Practice · 2023–now
RAG as default architecture
Retrieval-augmented generation as the answer to every knowledge problem — then "just stuff the window" as the counter-fad. Often right; often Postgres with pgvector would suffice.
$ Teams stood up vector pipelines, chunking strategies, and rerankers before asking if fine-tuning or a SQL query would answer the question. Retrieval infra became the product.