rag-architecture-patterns

id	SKL-rag-RAGARCHITECTUREPATTERNS
name	Rag Architecture Patterns
description	RAG (Retrieval-Augmented Generation) architecture patterns cover system design for building efficient, scalable, and accurate RAG systems. This skill covers data ingestion, chunking strategies, embedd
version	1.0.0
status	active
owner	@cerebra-team
last_updated	2026-02-22
category	Backend
tags	["api","backend","server","database"]
stack	["Python","Node.js","REST API","GraphQL"]
difficulty	Intermediate

Rag Architecture Patterns

Skill Profile

(Select at least one profile to enable specific modules)

• DevOps
• Backend
• Frontend
• AI-RAG
• Security Critical

Overview

RAG (Retrieval-Augmented Generation) architecture patterns cover system design for building efficient, scalable, and accurate RAG systems. This skill covers data ingestion, chunking strategies, embedding models, vector databases, retrieval optimization, and generation orchestration for production RAG applications.

Why This Matters

RAG systems combine the power of large language models with domain-specific knowledge, enabling accurate, context-aware responses grounded in actual data. Proper architecture design is critical for building production RAG systems that are accurate, fast, scalable, and cost-effective. Understanding chunking strategies, embedding model selection, vector database configuration, and retrieval optimization is essential for RAG success.

Core Concepts & Rules

1. Core Principles

• Follow established patterns and conventions
• Maintain consistency across codebase
• Document decisions and trade-offs

2. Implementation Guidelines

• Start with the simplest viable solution
• Iterate based on feedback and requirements
• Test thoroughly before deployment

Inputs / Outputs / Contracts

Skill Composition

• Depends on: None
• Compatible with: None
• Conflicts with: None
• Related Skills: None

Quick Start / Implementation Example

1. Review requirements and constraints
2. Set up development environment
3. Implement core functionality following patterns
4. Write tests for critical paths
5. Run tests and fix issues
6. Document any deviations or decisions

# Example implementation following best practices
 ():