<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Vector-Search on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/vector-search/</link>
		<description>Recent content in Vector-Search on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 21 Oct 2024 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/vector-search/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>RAG Is Not a Database Query</title>
				<link>https://dplabs.tech/blog/rag-is-not-a-database-query/</link>
				<pubDate>Mon, 21 Oct 2024 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/rag-is-not-a-database-query/</guid>
				<description>&lt;p&gt;Retrieval-Augmented Generation has become the default answer to &amp;ldquo;how do we make an LLM answer questions about our data.&amp;rdquo; The concept is simple enough to explain in one slide: embed your documents, store them in a vector database, retrieve the relevant ones at query time, pass them to the LLM.&lt;/p&gt;&#xA;&lt;p&gt;The problem is that the one-slide version produces one-slide-quality results. Good RAG systems are significantly harder to build than the demos suggest, and the failures are often subtle — the system produces confident, plausible-sounding answers that are wrong in ways that are hard to detect without systematic evaluation.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
