Build RAG Chatbot with Haystack, Pgvector, Amazon Bedrock Claude 3 Opus, and jina-clip-v2

Introduction to RAG

Retrieval-Augmented Generation (RAG) is a game-changer for GenAI applications, especially in conversational AI. It combines the power of pre-trained large language models (LLMs) like OpenAI’s GPT with external knowledge sources stored in vector databases such as Milvus and Zilliz Cloud, allowing for more accurate, contextually relevant, and up-to-date response generation. A RAG pipeline usually consists of four basic components: a vector database, an embedding model, an LLM, and a framework.

Key Components We'll Use for This RAG Chatbot

This tutorial shows you how to build a simple RAG chatbot in Python using the following components:

Haystack: An open-source Python framework designed for building production-ready NLP applications, particularly question answering and semantic search systems. Haystack excels at retrieving information from large document collections through its modular architecture that combines retrieval and reader components. Ideal for developers creating search applications, chatbots, and knowledge management systems that require efficient document processing and accurate information extraction from unstructured text.
Pgvector: an open-source extension for PostgreSQL that enables efficient storage and querying of high-dimensional vector data, essential for machine learning and AI applications. Designed to handle embeddings, it supports fast approximate nearest neighbor (ANN) searches using algorithms like HNSW and IVFFlat. Since it is just a vector search add-on to traditional search rather than a purpose-built vector database, it lacks scalability and availability and many other advanced features required by enterprise-level applications. Therefore, if you prefer a much more scalable solution or hate to manage your own infrastructure, we recommend using Zilliz Cloud, which is a fully managed vector database service built on the open-source Milvus and offers a free tier supporting up to 1 million vectors.)
AmazonBedrock Claude 3 Opus: A state-of-the-art multimodal AI model designed for complex reasoning, advanced data analysis, and high-stakes decision-making. Its strengths include deep contextual understanding, exceptional accuracy in processing text and images, and scalability for enterprise needs. Ideal for strategic planning, technical research, and sophisticated content generation requiring nuanced, ethical, and reliable outputs.
Jina-CLIP-V2: A multimodal AI model designed to seamlessly connect text and visual data, excelling in cross-modal retrieval tasks. Strengths include high accuracy in image-text matching, multilingual support, and scalable architecture. Ideal for semantic image search, content moderation, and personalized recommendations in e-commerce or media platforms.

By the end of this tutorial, you’ll have a functional chatbot capable of answering questions based on a custom knowledge base.

Note: Since we may use proprietary models in our tutorials, make sure you have the required API key beforehand.

Step 1: Install and Set Up Haystack

import os
import requests

from haystack import Pipeline
from haystack.components.converters import MarkdownToDocument

from haystack.components.preprocessors import DocumentSplitter
from haystack.components.writers import DocumentWriter

Step 2: Install and Set Up Amazon Bedrock Claude 3 Opus

Amazon Bedrock is a fully managed service that makes high-performing foundation models from leading AI startups and Amazon available through a unified API. You can choose from various foundation models to find the one best suited for your use case.

To use LLMs on Amazon Bedrock for text generation together with Haystack, you need to initialize an AmazonBedrockGenerator with the model name, the AWS credentials (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_DEFAULT_REGION) should be set as environment variables, be configured as described above or passed as Secret arguments. Note, make sure the region you set supports Amazon Bedrock.

Now, let's start installing and setting up models with Amazon Bedrock.

pip install amazon-bedrock-haystack

from haystack_integrations.components.generators.amazon_bedrock import AmazonBedrockGenerator

aws_access_key_id="..."
aws_secret_access_key="..."
aws_region_name="eu-central-1"

generator = AmazonBedrockGenerator(model="anthropic.claude-3-opus-20240229-v1:0")

Step 3: Install and Set Up jina-clip-v2

pip install jina-haystack

from haystack_integrations.components.embedders.jina import JinaTextEmbedder
from haystack_integrations.components.embedders.jina import JinaDocumentEmbedder

text_embedder = JinaTextEmbedder(api_key=Secret.from_token("<your-api-key>"), model="jina-clip-v2")
document_embedder = JinaDocumentEmbedder(api_key=Secret.from_token("<your-api-key>"), model="jina-clip-v2")

Step 4: Install and Set Up Pgvector

To quickly set up a PostgreSQL database with pgvector, you can use Docker:

docker run -d -p 5432:5432 -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres ankane/pgvector

To use pgvector with Haystack, install the pgvector-haystack integration:

pip install pgvector-haystack

import os
from haystack_integrations.document_stores.pgvector import PgvectorDocumentStore
from haystack_integrations.components.retrievers.pgvector import PgvectorEmbeddingRetriever

os.environ["PG_CONN_STR"] = "postgresql://postgres:postgres@localhost:5432/postgres"

document_store = PgvectorDocumentStore()
retriever = PgvectorEmbeddingRetriever(document_store=document_store)

Step 5: Build a RAG Chatbot

Now that you’ve set up all components, let’s start to build a simple chatbot. We’ll use the Milvus introduction doc as a private knowledge base. You can replace it your own dataset to customize your RAG chatbot.

url = 'https://raw.githubusercontent.com/milvus-io/milvus-docs/refs/heads/v2.5.x/site/en/about/overview.md'
example_file = 'example_file.md'
response = requests.get(url)
with open(example_file, 'wb') as f:
    f.write(response.content)
file_paths = [example_file]  # You can replace it with your own file paths.

indexing_pipeline = Pipeline()
indexing_pipeline.add_component("converter", MarkdownToDocument())
indexing_pipeline.add_component("splitter", DocumentSplitter(split_by="sentence", split_length=2))
indexing_pipeline.add_component("embedder", document_embedder)
indexing_pipeline.add_component("writer", DocumentWriter(document_store))
indexing_pipeline.connect("converter", "splitter")
indexing_pipeline.connect("splitter", "embedder")
indexing_pipeline.connect("embedder", "writer")
indexing_pipeline.run({"converter": {"sources": file_paths}})

# print("Number of documents:", document_store.count_documents())
  
question = "What is Milvus?"  # You can replace it with your own question.

retrieval_pipeline = Pipeline()
retrieval_pipeline.add_component("embedder", text_embedder)
retrieval_pipeline.add_component("retriever", retriever)
retrieval_pipeline.connect("embedder", "retriever")

retrieval_results = retrieval_pipeline.run({"embedder": {"text": question}})

# for doc in retrieval_results["retriever"]["documents"]:
#     print(doc.content)
#     print("-" * 10)

from haystack.utils import Secret
from haystack.components.builders import PromptBuilder

retriever = PgvectorEmbeddingRetriever(document_store=document_store) 
 text_embedder = JinaTextEmbedder(api_key=Secret.from_token("<your-api-key>"), model="jina-clip-v2")

prompt_template = """Answer the following query based on the provided context. If the context does
                     not include an answer, reply with 'I don't know'.\n
                     Query: {{query}}
                     Documents:
                     {% for doc in documents %}
                        {{ doc.content }}
                     {% endfor %}
                     Answer: 
                  """

rag_pipeline = Pipeline()
rag_pipeline.add_component("text_embedder", text_embedder)
rag_pipeline.add_component("retriever", retriever)
rag_pipeline.add_component("prompt_builder", PromptBuilder(template=prompt_template))
rag_pipeline.add_component("generator", generator)
rag_pipeline.connect("text_embedder.embedding", "retriever.query_embedding")
rag_pipeline.connect("retriever.documents", "prompt_builder.documents")
rag_pipeline.connect("prompt_builder", "generator")

results = rag_pipeline.run({"text_embedder": {"text": question}, "prompt_builder": {"query": question},})
print('RAG answer:\n', results["generator"]["replies"][0])

Optimization Tips

As you build your RAG system, optimization is key to ensuring peak performance and efficiency. While setting up the components is an essential first step, fine-tuning each one will help you create a solution that works even better and scales seamlessly. In this section, we’ll share some practical tips for optimizing all these components, giving you the edge to build smarter, faster, and more responsive RAG applications.

Haystack optimization tips

To optimize Haystack in a RAG setup, ensure you use an efficient retriever like FAISS or Milvus for scalable and fast similarity searches. Fine-tune your document store settings, such as indexing strategies and storage backends, to balance speed and accuracy. Use batch processing for embedding generation to reduce latency and optimize API calls. Leverage Haystack's pipeline caching to avoid redundant computations, especially for frequently queried documents. Tune your reader model by selecting a lightweight yet accurate transformer-based model like DistilBERT to speed up response times. Implement query rewriting or filtering techniques to enhance retrieval quality, ensuring the most relevant documents are retrieved for generation. Finally, monitor system performance with Haystack’s built-in evaluation tools to iteratively refine your setup based on real-world query performance.

pgvector optimization tips

To optimize pgvector in a Retrieval-Augmented Generation (RAG) setup, consider indexing your vectors using GiST or IVFFlat to significantly speed up search queries and improve retrieval performance. Make sure to leverage parallelization for query execution, allowing multiple queries to be processed simultaneously, especially for large datasets. Optimize memory usage by tuning the vector storage size and using compressed embeddings where possible. To further enhance query speed, implement pre-filtering techniques to narrow down search space before querying. Regularly rebuild indexes to ensure they are up to date with any new data. Fine-tune vectorization models to reduce dimensionality without sacrificing accuracy, thus improving both storage efficiency and retrieval times. Finally, manage resource allocation carefully, utilizing horizontal scaling for larger datasets and offloading intensive operations to dedicated processing units to maintain responsiveness during high-traffic periods.

AmazonBedrock Claude 3 Opus optimization tips

To optimize Claude 3 Opus in RAG, focus on efficient retrieval and context management. Use smaller, semantically dense document chunks (200-400 tokens) to improve relevance and reduce noise. Implement metadata filtering during retrieval to prioritize high-quality sources. Fine-tune prompts with explicit instructions to leverage Claude’s reasoning, such as asking for step-by-step analysis or citing retrieved passages. Adjust temperature and top-p settings to balance creativity and accuracy. Cache frequent queries to reduce latency and costs, and monitor token usage via Amazon Bedrock’s metrics to optimize chunk sizes or batch processing. Regularly validate outputs against ground-truth data to refine retrieval thresholds and prompt engineering.

Jina-CLIP-v2 optimization tips

To optimize Jina-CLIP-v2 in a RAG setup, preprocess inputs by cleaning text, normalizing formats, and truncating overly long documents to reduce noise. Use batch inference for embeddings to leverage GPU parallelism, and ensure model weights are quantized or pruned for faster inference. Cache frequently accessed embeddings to avoid redundant computations. Fine-tune the model on domain-specific data to improve retrieval relevance. Pair with efficient vector indexes (e.g., FAISS) for low-latency similarity searches, and monitor embedding quality via recall metrics to balance speed and accuracy. Regularly update the index with fresh data.

By implementing these tips across your components, you'll be able to enhance the performance and functionality of your RAG system, ensuring it’s optimized for both speed and accuracy. Keep testing, iterating, and refining your setup to stay ahead in the ever-evolving world of AI development.

RAG Cost Calculator: A Free Tool to Calculate Your Cost in Seconds

Estimating the cost of a Retrieval-Augmented Generation (RAG) pipeline involves analyzing expenses across vector storage, compute resources, and API usage. Key cost drivers include vector database queries, embedding generation, and LLM inference.

RAG Cost Calculator is a free tool that quickly estimates the cost of building a RAG pipeline, including chunking, embedding, vector storage/search, and LLM generation. It also helps you identify cost-saving opportunities and achieve up to 10x cost reduction on vector databases with the serverless option.

Calculate your RAG cost now.

Calculate your RAG cost

What Have You Learned?

You’ve just unlocked the power to build a cutting-edge RAG system by weaving together four game-changing components! By now, you’ve seen how Haystack acts as the backbone, orchestrating every step of the pipeline with its modular design—from ingesting data to generating answers. You’ve harnessed Pgvector, PostgreSQL’s vector extension, to store and retrieve embeddings at lightning speed, turning your database into a dynamic knowledge hub. Then there’s Amazon Bedrock’s Claude 3 Opus, the LLM powerhouse that transforms retrieved context into human-like responses, blending creativity with precision. And let’s not forget jina-clip-v2, the embedding model that converts text and images into rich numerical representations, ensuring your system understands context deeply and accurately. Together, these tools create a seamless flow: data becomes embeddings, embeddings find relevance in Pgvector, and Claude 3 Opus crafts answers that feel almost magical!

But wait—there’s more! You’ve also picked up pro tips for optimizing your RAG pipeline, like tuning chunk sizes for balance between speed and accuracy, and leveraging metadata filtering to sharpen results. Plus, that free RAG cost calculator you explored? It’s your secret weapon for estimating expenses and scaling smarter. Now, imagine what you can build: customer support bots that truly understand, research assistants that dig deeper, or even multimedia search engines that bridge text and images. The future of intelligent applications is in your hands. So go ahead—experiment fearlessly, tweak relentlessly, and innovate boldly. Your next RAG project isn’t just possible; it’s inevitable. Let’s turn those ideas into reality, one vector at a time! 🚀

Further Resources

🌟 In addition to this RAG tutorial, unleash your full potential with these incredible resources to level up your RAG skills.

How to Build a Multimodal RAG | Documentation
How to Enhance the Performance of Your RAG Pipeline
Graph RAG with Milvus | Documentation
How to Evaluate RAG Applications - Zilliz Learn
Generative AI Resource Hub | Zilliz

We'd Love to Hear What You Think!

We’d love to hear your thoughts! 🌟 Leave your questions or comments below or join our vibrant Milvus Discord community to share your experiences, ask questions, or connect with thousands of AI enthusiasts. Your journey matters to us!

If you like this tutorial, show your support by giving our Milvus GitHub repo a star ⭐—it means the world to us and inspires us to keep creating! 💖