-
Notifications
You must be signed in to change notification settings - Fork 892
feat(docs): add component architecture documentation #1226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
de3576e
feat(docs): add component architecture documentation
mdrxy 3796201
Update src/oss/langchain/component-architecture.mdx
mdrxy 879833b
Update src/oss/langchain/component-architecture.mdx
mdrxy 9fc3915
Merge branch 'main' into mdrxy/component-diagram
mdrxy e163866
docs.json
mdrxy a14de4d
cr
mdrxy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,121 @@ | ||
| --- | ||
| title: Component architecture | ||
| --- | ||
|
|
||
| LangChain's power comes from how its components work together to create sophisticated AI applications. This page provides diagrams showcasing the relationships between different components. | ||
|
|
||
| ## Core component ecosystem | ||
|
|
||
| The diagram below shows how LangChain's major components connect to form complete AI applications: | ||
|
|
||
| ```mermaid | ||
| graph TD | ||
| %% Input processing | ||
| subgraph "📥 Input processing" | ||
| A[Text input] --> B[Document loaders] | ||
| B --> C[Text splitters] | ||
| C --> D[Documents] | ||
| end | ||
|
|
||
| %% Embedding & storage | ||
| subgraph "🔢 Embedding & storage" | ||
| D --> E[Embedding models] | ||
| E --> F[Vectors] | ||
| F --> G[(Vector stores)] | ||
| end | ||
|
|
||
| %% Retrieval | ||
| subgraph "🔍 Retrieval" | ||
| H[User Query] --> I[Embedding models] | ||
| I --> J[Query vector] | ||
| J --> K[Retrievers] | ||
| K --> G | ||
| G --> L[Relevant context] | ||
| end | ||
|
|
||
| %% Generation | ||
| subgraph "🤖 Generation" | ||
| M[Chat models] --> N[Tools] | ||
| N --> O[Tool results] | ||
| O --> M | ||
| L --> M | ||
| M --> P[AI response] | ||
| end | ||
|
|
||
| %% Orchestration | ||
| subgraph "🎯 Orchestration" | ||
| Q[Agents] --> M | ||
| Q --> N | ||
| Q --> K | ||
| Q --> R[Memory] | ||
| end | ||
| ``` | ||
|
|
||
| ### How components connect | ||
|
|
||
| Each component layer builds on the previous ones: | ||
|
|
||
| 1. **Input processing** – Transform raw data into structured documents | ||
| 2. **Embedding & storage** – Convert text into searchable vector representations | ||
| 3. **Retrieval** – Find relevant information based on user queries | ||
| 4. **Generation** – Use AI models to create responses, optionally with tools | ||
| 5. **Orchestration** – Coordinate everything through agents and memory systems | ||
|
|
||
| ## Component categories | ||
|
|
||
| LangChain organizes components into these main categories: | ||
|
|
||
| | Category | Purpose | Key Components | Use Cases | | ||
| |----------|---------|---------------|-----------| | ||
| | **[Models](/oss/langchain/models)** | AI reasoning and generation | Chat models, LLMs, Embedding models | Text generation, reasoning, semantic understanding | | ||
| | **[Tools](/oss/langchain/tools)** | External capabilities | APIs, databases, etc. | Web search, data access, computations | | ||
| | **[Agents](/oss/langchain/agents)** | Orchestration and reasoning | ReAct agents, tool calling agents | Nondeterministic workflows, decision making | | ||
| | **[Memory](/oss/langchain/short-term-memory)** | Context preservation | Message history, custom state | Conversations, stateful interactions | | ||
| | **[Retrievers](/oss/integrations/retrievers)** | Information access | Vector retrievers, web retrievers | RAG, knowledge base search | | ||
| | **[Document processing](/oss/integrations/document_loaders)** | Data ingestion | Loaders, splitters, transformers | PDF processing, web scraping | | ||
| | **[Vector Stores](/oss/integrations/vectorstores)** | Semantic search | Chroma, Pinecone, FAISS | Similarity search, embeddings storage | | ||
|
|
||
| ## Common patterns | ||
|
|
||
| ### RAG (Retrieval-Augmented Generation) | ||
| ```mermaid | ||
| graph LR | ||
| A[User question] --> B[Retriever] | ||
| B --> C[Relevant docs] | ||
| C --> D[Chat model] | ||
| A --> D | ||
| D --> E[Informed response] | ||
| ``` | ||
|
|
||
| ### Agent with tools | ||
| ```mermaid | ||
| graph LR | ||
| A[User request] --> B[Agent] | ||
| B --> C{Need tool?} | ||
| C -->|Yes| D[Call tool] | ||
| D --> E[Tool result] | ||
| E --> B | ||
| C -->|No| F[Final answer] | ||
| ``` | ||
|
|
||
| ### Multi-agent system | ||
| ```mermaid | ||
| graph LR | ||
| A[Complex Task] --> B[Supervisor agent] | ||
| B --> C[Specialist agent 1] | ||
| B --> D[Specialist agent 2] | ||
| C --> E[Results] | ||
| D --> E | ||
| E --> B | ||
| B --> F[Coordinated response] | ||
| ``` | ||
|
|
||
| ## Learn more | ||
|
|
||
| Now that you understand how components relate to each other, explore specific areas: | ||
|
|
||
| - [Building your first RAG system](/oss/langchain/knowledge-base) | ||
| - [Creating agents](/oss/langchain/agents) | ||
| - [Working with tools](/oss/langchain/tools) | ||
| - [Setting up memory](/oss/langchain/short-term-memory) | ||
| - [Browse integrations](/oss/integrations/providers/overview) | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The frontmatter is missing a required
descriptionfield. According to the documentation guidelines, all MDX files must include bothtitleanddescriptionin their frontmatter. Add a concise description that will be used for SEO and navigation purposes.