<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>KoedoDB Blog</title>
    <link>https://koedodb.com/blog/</link>
    <description>Notes from building KoedoDB.</description>
    <item><title>runc, gVisor, Kata and our own microVM runtime: the same PostgreSQL and nginx, measured</title><link>https://koedodb.com/blog/runtime-comparison/</link><guid>https://koedodb.com/blog/runtime-comparison/</guid><pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate><description>runc, gVisor, Kata and our own microVM runtime, with the same CPU, memory and load: PostgreSQL, nginx and memory cost. We built one of them, and we say where it loses.</description></item>
    <item><title>Why KoedoDB runs on dedicated servers</title><link>https://koedodb.com/blog/why-dedicated-servers/</link><guid>https://koedodb.com/blog/why-dedicated-servers/</guid><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><description>Why we rent whole servers instead of cloud virtual machines: steady performance, a database in its own virtual machine, and no surprise maintenance. And what it costs us.</description></item>
    <item><title>How KoedoDB keeps one project away from another</title><link>https://koedodb.com/blog/how-we-isolate-projects/</link><guid>https://koedodb.com/blog/how-we-isolate-projects/</guid><pubDate>Tue, 06 Oct 2026 00:00:00 GMT</pubDate><description>The design behind project isolation: a namespace, a database and keys per project, a sandbox for your code, and a network that is closed by default.</description></item>
  </channel>
</rss>
