<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Microservices on PAUL&#39;S BLOG</title>
    <link>https://paulyu.dev/tags/microservices/</link>
    <description>Recent content in Microservices on PAUL&#39;S BLOG</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 11 Sep 2022 06:00:00 -0700</lastBuildDate>
    <atom:link href="https://paulyu.dev/tags/microservices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Autoscaling Azure Container Apps</title>
      <link>https://paulyu.dev/article/azure-container-apps-autoscaling/</link>
      <pubDate>Sun, 11 Sep 2022 06:00:00 -0700</pubDate>
      <guid>https://paulyu.dev/article/azure-container-apps-autoscaling/</guid>
      <description>&lt;h2 id=&#34;so-what-makes-azure-container-apps-serverless&#34;&gt;So, what makes Azure Container Apps &amp;ldquo;serverless&amp;rdquo;?&lt;/h2&gt;&#xA;&lt;p&gt;Today we are going to focus on what makes Azure Container Apps (ACA) a &amp;ldquo;serverless&amp;rdquo; offering. But what does the term &amp;ldquo;&lt;em&gt;serverless&lt;/em&gt;&amp;rdquo; really mean? As much as we&amp;rsquo;d like to think there aren&amp;rsquo;t any servers involved, that is certainly not the case. In general, &amp;ldquo;serverless&amp;rdquo; means that most (if not all) server maintenance has been abstracted away from you.&lt;/p&gt;&#xA;&lt;p&gt;With serverless, you don&amp;rsquo;t spend any time managing and patching servers. This concern is offloaded to Azure and you simply focus on adding business value through application delivery. In addition to operational efficiency, cost efficiency can be achieved with serverless on-demand pricing models. Your workload horizontally scales out based on need and you only pay for what you use. To me, this is &lt;strong&gt;serverless&lt;/strong&gt;, and my teammate &lt;a href=&#34;https://github.com/smurawski&#34;&gt;@StevenMurawski&lt;/a&gt; said it best&amp;hellip; &amp;ldquo;&lt;em&gt;being able to &lt;strong&gt;scale to zero&lt;/strong&gt; is what gives ACA it&amp;rsquo;s serverless magic&lt;/em&gt;.&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microservices Communications with Azure Container Apps</title>
      <link>https://paulyu.dev/article/azure-container-apps-microservices-communication/</link>
      <pubDate>Sat, 10 Sep 2022 06:00:00 -0700</pubDate>
      <guid>https://paulyu.dev/article/azure-container-apps-microservices-communication/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;In yesterday&amp;rsquo;s &lt;a href=&#34;https://azure.github.io/Cloud-Native/blog/08-containerapps-intro&#34;&gt;#ServerlessSeptember&lt;/a&gt; post, we learned what the Azure Container Apps (ACA) service is and the problems it aims to solve. It is considered to be a Container-as-a-Service platform since much of the complex implementation details of running a Kubernetes cluster is managed for you.&lt;/p&gt;&#xA;&lt;p&gt;Some of the use cases for ACA include event-driven processing jobs and background tasks, but this article will focus on hosting microservices, and how they can communicate with each other within the ACA service. At the end of this article, you will have a solid understanding of how networking and communication is handled and will leave you with a few tutorials to try.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
