<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Michael Seliger – Insights</title>
    <link>https://michaelseliger.com/en/insights</link>
    <description>Articles on software architecture, cloud, e-commerce and team leadership in mid-sized companies — assessments from real projects, about once a month.</description>
    <language>en</language>
    <atom:link href="https://michaelseliger.com/en/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Expo over native — lessons learned from a cross-platform app</title>
      <link>https://michaelseliger.com/en/insights/2026-03-expo-statt-native-lessons-learned</link>
      <guid isPermaLink="true">https://michaelseliger.com/en/insights/2026-03-expo-statt-native-lessons-learned</guid>
      <description>For most apps, Expo is enough — faster, cheaper, one codebase. And it brings infrastructure you would otherwise have to build yourself. Where it delivered, where it hurt, and when it has to be native after all.</description>
      <category>Architecture</category>
      <pubDate>Wed, 11 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Astro over Next.js — the frontend decision that mostly never gets made</title>
      <link>https://michaelseliger.com/en/insights/2026-02-astro-vs-nextjs-marketing-sites</link>
      <guid isPermaLink="true">https://michaelseliger.com/en/insights/2026-02-astro-vs-nextjs-marketing-sites</guid>
      <description>When picking a frontend, teams often only weigh the &quot;big&quot; ones — Next, Nuxt and the like. For websites, landing and marketing pages, Astro is frequently the better choice on maintenance, performance and bloat. An assessment — using this site as the example.</description>
      <category>Architecture</category>
      <pubDate>Wed, 11 Feb 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The mid-market stack, part 3: serverless in house — functions without Cloudflare</title>
      <link>https://michaelseliger.com/en/insights/2026-01-mittelstand-stack-serverless-dokploy</link>
      <guid isPermaLink="true">https://michaelseliger.com/en/insights/2026-01-mittelstand-stack-serverless-dokploy</guid>
      <description>Cloudflare Workers are technically excellent — and still put some companies off. How to get functions behind a URL just as easily, without leaving your own stack. The finale of the mid-market stack series.</description>
      <category>Architecture</category>
      <pubDate>Wed, 14 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The mid-market stack, part 2: Terraform for small teams — when it starts to pay off</title>
      <link>https://michaelseliger.com/en/insights/2025-12-mittelstand-stack-terraform-kleine-teams</link>
      <guid isPermaLink="true">https://michaelseliger.com/en/insights/2025-12-mittelstand-stack-terraform-kleine-teams</guid>
      <description>Clicking it together is faster — until a few months later nobody knows what is actually running. Why Terraform pays off from the very first person in the IT team, and where it turns into an overhead trap. Part 2 of the mid-market stack series.</description>
      <category>Cloud</category>
      <pubDate>Wed, 10 Dec 2025 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The mid-market stack, part 1: Hetzner instead of a hyperscaler — when it is enough, when it is not</title>
      <link>https://michaelseliger.com/en/insights/2025-11-mittelstand-stack-hetzner-statt-hyperscaler</link>
      <guid isPermaLink="true">https://michaelseliger.com/en/insights/2025-11-mittelstand-stack-hetzner-statt-hyperscaler</guid>
      <description>&quot;Cloud&quot; reflexively means AWS or Google for many mid-sized companies. That is often the most expensive answer to a question nobody asked. Part 1 of a series on a modern, affordable stack without enterprise overhead.</description>
      <category>Cloud</category>
      <pubDate>Wed, 12 Nov 2025 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Choosing a CMS in 2025: when enterprise, when open source — an assessment.</title>
      <link>https://michaelseliger.com/en/insights/2025-10-cms-auswahl-enterprise-open-source</link>
      <guid isPermaLink="true">https://michaelseliger.com/en/insights/2025-10-cms-auswahl-enterprise-open-source</guid>
      <description>AEM-certified, Magento certified — and my own project runs on open source. Not a contradiction, but exactly the question every CMS decision is really about. An assessment from fifteen years of selection processes.</description>
      <category>E-commerce</category>
      <pubDate>Wed, 08 Oct 2025 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What I keep from 15 years in an agency — and what I now do deliberately differently.</title>
      <link>https://michaelseliger.com/en/insights/2025-09-agentur-learnings</link>
      <guid isPermaLink="true">https://michaelseliger.com/en/insights/2025-09-agentur-learnings</guid>
      <description>After fifteen years of agency work and team leadership, I drew a line in early 2025 and started out solo. Not a break with the past — more a deliberate inventory: what was genuinely good, what was only habit, and what cost more energy than it was worth.</description>
      <category>Leadership</category>
      <pubDate>Wed, 10 Sep 2025 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
