Retrieval-augmented generation (RAG)
Best suited to: Applications answering questions about frequently changing documents
Retrieve relevant documents at query time and supply selected material to the model.
Three different engineering choices address access to knowledge, model behaviour and prompt capacity; compare the failure modes before budgeting.
Retrieve relevant documents at query time and supply selected material to the model.
Adapt model behaviour using curated training examples.
Verification Methodology: Analyzed enterprise LLM architectural trade-offs, knowledge retrieval latency, parametric memory adaptation, and cost economics across published computer science research and engineering implementations.
Scope & Limitations: Compute costs, latency tolerance, and document update frequency determine the appropriate architecture.
This guide does not score you or choose a winner. It summarizes the reviewed use-case notes for each option so you can decide which trade-off matters most.
Compare key specifications, verified benchmarks, and technical parameters side by side based on official documentation and verified reference sources. Missing values are shown as Unknown.
| Feature / parameter | Retrieval-augmented generation (RAG)Not directly comparable | Fine-tuningNot directly comparable |
|---|---|---|
Where knowledge resides | External indexed source documents | Behaviour learned from examples |
Updating a changed policy | Re-index changed documents | Usually still requires external facts, not only new training |
Quality failure to measure | Wrong passage retrieved or omitted | Overfitting and hallucinated facts |
Main ongoing cost | Search, indexing, inference | Training runs plus inference |
Evidence traceability | Can cite retrieved source offsets | Not intrinsic to parameter updates |
Beyond raw specifications, these are the fundamental architectural, philosophical, and day-to-day distinctions that matter most.
Training on a handbook will not reliably preserve every date, number and policy update.
Compare cost per correct answer rather than token price alone.
Evaluated on enterprise AI architecture requirements. RAG provides verifiable, low-latency grounding on dynamic private data, fine-tuning teaches models specialized styles or narrow domain vocabularies, and long-context windows enable zero-shot document reasoning without vector database indexing.
Common queries, buying considerations, and key answers regarding this comparison.