<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vector-Database on Shaharia Azam&#39;s Website | DevOps, Platform Engineering &amp; AI Insights</title>
    <link>https://shaharia.com/tags/vector-database/</link>
    <description>Recent content in Vector-Database on Shaharia Azam&#39;s Website | DevOps, Platform Engineering &amp; AI Insights</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 25 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://shaharia.com/tags/vector-database/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Choosing an Embeddable Vector Database for a Go Application</title>
      <link>https://shaharia.com/blog/choosing-embeddable-vector-database-go-application/</link>
      <pubDate>Sat, 25 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://shaharia.com/blog/choosing-embeddable-vector-database-go-application/</guid>
      <description>If you are shipping a Go application that runs on a user&amp;rsquo;s machine and needs vector search, you face an awkward problem: most popular vector databases (Chroma, Qdrant, Weaviate, Milvus, Pinecone) run as separate servers. That means asking your users to install and operate extra infrastructure, which is a non-starter for a single-binary developer tool.&#xA;This post walks through the embeddable options I evaluated, the trade-offs, and a decision tree to help you pick one for your own project.</description>
    </item>
  </channel>
</rss>
