<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>dawit.blog — Articles</title>
    <link>https://dawit.blog/articles</link>
    <description>Essays and engineering notes by Dawit Abate Woldeamanuel — cloud sovereignty, European infrastructure, open source and applied AI.</description>
    <language>en</language>
    <managingEditor>dawit@gojodigital.com (Dawit Abate Woldeamanuel)</managingEditor>
    <webMaster>dawit@gojodigital.com (Dawit Abate Woldeamanuel)</webMaster>
    <copyright>© 2026 Dawit Abate Woldeamanuel</copyright>
    <lastBuildDate>Thu, 15 Oct 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://dawit.blog/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why I built Flui</title>
      <link>https://dawit.blog/articles/why-i-built-flui</link>
      <guid isPermaLink="false">https://dawit.blog/articles/why-i-built-flui</guid>
      <description>What does it take today to build a cloud platform? From Docker Compose and K3s to a platform that composes existing providers instead of replacing them.</description>
      <content:encoded><![CDATA[What does it take today to build a cloud platform? I’ve spent a good part of my career using the best cloud services available. I’ve always appreciated their convenience, efficiency, comprehensiveness, and power—but above all, the user experience. Behind those few simple steps—configuring a scaling group, managing a private network or a firewall, creating a managed database with a single click—lies a tremendous amount of work that we take for granted. While I’ve used hyperscaler services professionally, for various self-funded personal and entrepreneurial projects I’ve opted for VPS or dedicated servers, following a path many have taken: deploying via FTP, then using Docker containers, and finally Docker Compose to manage an application that was starting to grow more complex. A database, a backend, a frontend, a Redis cache. At this stage, it was already possible to manage replicas of API components. Even as projects became more complex—with microservices, different types of databases, and queue management systems—I was still able to manage them with Compose. I reached a limit when I had to manage multiple projects simultaneously across different servers. I felt the need for…]]></content:encoded>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
      <dc:creator>Dawit Abate Woldeamanuel</dc:creator>
      <category>Flui</category>
      <category>Cloud</category>
      <category>Kubernetes</category>
      <category>Infrastructure</category>
      <category>Open Source</category>
    </item>
  </channel>
</rss>
