0Pricing
LangChain / RAG / Vector DBs · 课时

向量数据库的持久化与可扩展性

学习确保数据持久性、处理大型数据集，以及为生产工作负载扩展向量数据库的策略。

向量数据库的持久化与可扩展性 是 CoddyKit 上的免费 LangChain / RAG / Vector DBs 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 LangChain / RAG / Vector DBs 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 LangChain / RAG / Vector DBs 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Data That Stays: Persistence

In this lesson, we'll explore two crucial concepts for any production-ready vector database: Persistence and Scalability.

Imagine building a powerful search engine. You wouldn't want to lose all your indexed data every time the system restarts, right? That's where persistence comes in!

What is Persistence?

Persistence means your data survives even if the application or server shuts down. It's saved to a durable storage like a disk, not just kept in temporary memory.

  • Why it matters: Prevents data loss.
  • Without it: All your carefully generated vector embeddings would vanish on restart.
  • Goal: Ensure data durability and reliability.

File-Based Persistence

A common way to achieve persistence is by saving the vector index and associated data directly to files on a disk. This is often seen in local or embedded vector databases.

  • How it works: Data is written to specific file formats (e.g., binary files, HDF5).
  • Pros: Simple to implement for smaller datasets.
  • Cons: Can be slower for very large datasets, manual management required.

Code: ChromaDB Persistence

Let's see a simple example of a persistent vector store using ChromaDB. It saves your collections to a local directory, so your data is safe across sessions.

import chromadb

# Initialize a persistent client
# This creates a 'my_vector_db' directory if it doesn't exist
client = chromadb.PersistentClient(path="./my_vector_db")

# Get or create a collection (like a table)
collection = client.get_or_create_collection(name="lesson_docs")

# Add some data to the collection
collection.add(
    documents=["LangChain helps build LLM apps", "Vector DBs store embeddings"],
    metadatas=[{"source": "lesson"}, {"source": "course"}],
    ids=["doc1", "doc2"]
)

print("Documents added to persistent ChromaDB.")
print("Check the 'my_vector_db' directory!")

# You can query it immediately or after restarting your script
results = collection.query(
    query_texts=["LLM applications"],
    n_results=1
)
print("\nQuery Results:")
print(results["documents"][0][0])

Persistence with Backing DBs

Some vector databases use traditional databases (like PostgreSQL or SQLite) as their underlying persistence layer. The vector data might be stored in a special column type (e.g., pgvector extension for PostgreSQL).

  • Benefits: Leverages existing database features like transactions, backups, and replication.
  • Example: pgvector allows PostgreSQL to store and query vector embeddings efficiently.

Scaling Your Vector DB

Scalability refers to a system's ability to handle a growing amount of work—more data, more users, more queries—without a significant drop in performance.

  • Why it matters: Your application's success means more data and users.
  • Goal: Maintain fast search speeds and reliability as your system grows.

Vertical Scaling: Grow Up

Vertical scaling (or 'scaling up') means adding more resources (CPU, RAM, faster storage) to a single server. Think of it as making one machine super powerful.

  • Pros: Often simpler to manage initially.
  • Cons: There's a limit to how powerful a single machine can be. It also creates a single point of failure.

Horizontal Scaling: Grow Out

Horizontal scaling (or 'scaling out') means distributing your data and workload across multiple servers. This is how large-scale cloud services operate.

  • Sharding: Splitting your entire dataset into smaller, independent pieces (shards) and storing each shard on a different server.
  • Replication: Creating copies of your data/index across multiple servers for fault tolerance and to handle more read requests.

Trade-offs in Scaling

Choosing a scaling strategy involves trade-offs:

  • Cost: More servers generally mean higher costs.
  • Complexity: Distributed systems are inherently more complex to design, build, and maintain.
  • Performance: Scaling can improve performance but also introduce network latency.
  • Consistency: Ensuring all copies of data are identical can be challenging in distributed systems.

Quick Check on Concepts

Which of the following statements accurately describe concepts related to vector database persistence and scalability?

Lesson Summary

You've learned about the critical roles of persistence and scalability in vector databases. Persistence ensures your valuable embeddings are never lost, while scalability allows your system to grow and handle increasing demands.

Understanding these concepts helps you choose and design robust vector database solutions for production applications.

常见问题解答

「向量数据库的持久化与可扩展性」课时是免费的吗？

是的 — 「向量数据库的持久化与可扩展性」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 LangChain / RAG / Vector DBs 课程的其余内容，请升级到 CoddyKit PRO。 LangChain / RAG / Vector DBs 课程共包含 4 节课。

「向量数据库的持久化与可扩展性」这节课中我会学到什么？

学习确保数据持久性、处理大型数据集，以及为生产工作负载扩展向量数据库的策略。 你通过在浏览器中直接运行的动手代码来练习 LangChain / RAG / Vector DBs，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 LangChain / RAG / Vector DBs 需要有经验吗？

无需任何先前经验。CoddyKit 上的 LangChain / RAG / Vector DBs 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。

「向量数据库的持久化与可扩展性」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 LangChain / RAG / Vector DBs 课中编写并运行代码吗？

能。每节 LangChain / RAG / Vector DBs 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 向量 DB 存储架构
  2. 近邻搜索算法（HNSW、IVFFlat）
  3. 向量数据库的持久化与可扩展性
  4. 向量量化与压缩
← 返回 LangChain / RAG / Vector DBs