<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Azure Container Apps on Wolkwacht</title>
    <link>https://wolkwacht.nl/topics/azure-container-apps/</link>
    <description>Recent content in Azure Container Apps on Wolkwacht</description>
    <image>
      <title>Wolkwacht</title>
      <url>https://wolkwacht.nl/images/branding/feature-image.png</url>
      <link>https://wolkwacht.nl/images/branding/feature-image.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://wolkwacht.nl/topics/azure-container-apps/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Is Azure Container Apps Eating AKS&#39;s Lunch for Smaller Workloads?</title>
      <link>https://wolkwacht.nl/posts/2026-09-04_is-azure-container-apps-eating-akss-lunch-for-smaller-workloads/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/2026-09-04_is-azure-container-apps-eating-akss-lunch-for-smaller-workloads/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;A small set of containerized services chooses between a lightweight managed platform and a more sophisticated Kubernetes platform&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/aca-vs-aks-feature.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Kubernetes has become so familiar that many teams don&amp;rsquo;t choose to adopt it anymore; they just start using it. When a new internal API appears, someone sets up an AKS cluster, and within weeks, the team manages node pools, upgrade channels, ingress, identity, policies, observability, and a backlog of Helm charts. None of these decisions are incorrect, but the issue is that the workload might never have required a Kubernetes platform in the first place.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Optimizing Azure Container Apps Costs: Scaling to Zero, Workload Profiles, and FinOps</title>
      <link>https://wolkwacht.nl/posts/optimizing-azure-container-apps-costs-scaling-to-zero-workload-profiles-and-finops/</link>
      <pubDate>Tue, 16 Jun 2026 09:56:49 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/optimizing-azure-container-apps-costs-scaling-to-zero-workload-profiles-and-finops/</guid>
      <description>Azure Container Apps enables teams to deploy APIs, background processors, scheduled jobs, and event-driven services without directly…</description>
    </item>
    <item>
      <title>From Code to Cloud: A Hands-On Guide to Azure Container Apps</title>
      <link>https://wolkwacht.nl/posts/from-code-to-cloud-a-hands-on-guide-to-azure-container-apps/</link>
      <pubDate>Thu, 03 Apr 2025 14:48:31 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/from-code-to-cloud-a-hands-on-guide-to-azure-container-apps/</guid>
      <description>&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://cdn-images-1.medium.com/max/800/1*cOYo_ORmMItNjJcD3xKyJg.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;As a cloud professional, I constantly seek ways to streamline application delivery while reducing operational overhead. Whether you’re building APIs, microservices, or event-driven backends, choosing the right platform can significantly impact speed to market and maintainability.&lt;/p&gt;
&lt;p&gt;Introducing Azure Container Apps (ACA) — a fully managed, serverless platform designed specifically for running containerized workloads without the complexity of orchestrating and managing Kubernetes infrastructure. Built on top of Kubernetes and powered by open-source technologies like &lt;a href=&#34;https://dapr.io&#34;&gt;Dapr&lt;/a&gt; and &lt;a href=&#34;https://keda.sh/&#34;&gt;KEDA&lt;/a&gt; (Kubernetes Event Driven Autoscaling), ACA offers the best of both worlds: the power and flexibility of containers with the simplicity and developer focus of a Platform-as-a-Service (PaaS).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
