The RAG stack

Retrieval-augmented generation grounds an LLM in your own data. A production RAG pipeline is four layers: ingestion, a vector store, orchestration, and evaluation.

GraphCanon updated 2d · 104 views this month

Ingestion & retrieval - parse, chunk, and load documents into a retrievable form.

When not to use: Skip a heavy ingestion framework when your corpus is small and static; a script plus the embedding API is enough.

Vector store - persist embeddings and run similarity search at query time.

When not to use: Don't reach for a dedicated vector DB under ~100k vectors; pgvector on your existing Postgres is simpler to operate.

Orchestration - assemble retrieval, prompting, and the model into a chain.

When not to use: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.

Evaluation & tracing - measure answer quality, cost, and latency before and after changes.

When not to use: Defer heavyweight eval infra only until you have real traffic - never skip it once users depend on answers.

Common questions

What is the the rag stack?
Retrieval-augmented generation grounds an LLM in your own data. A production RAG pipeline is four layers: ingestion, a vector store, orchestration, and evaluation.
When should I use the the rag stack?
Use this stack when your constraints match its layers: Data & Retrieval, Vector Databases, LLM Frameworks, Evaluation & Observability. Each step on the page includes when-not-to-use guidance so you do not over-engineer.
How does GraphCanon pick tools for the rag stack?
Stack pages are editorial workflows over canonical categories. Representative tools are pulled live from the graph at render time (top adoption in each category), not a fixed marketing list.
Where can I compare tools in this stack?
Follow category hubs and head-to-head compare pages linked from each step. Featured comparisons cover the highest-intent pairs (frameworks, vector DBs, agent runtimes). Start at compare hub.
Is there a machine-readable version of The RAG stack?
Yes. Append .md to `/stacks/rag-pipeline` or fetch `/md/stacks/rag-pipeline` for a markdown twin with steps, when-not notes, and tool links.

Was this helpful?

Anonymous feedback helps us improve pages and translations.