<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Akshay Chavan</title>
    <description>The latest articles on DEV Community by Akshay Chavan (@aksh11).</description>
    <link>https://dev.to/aksh11</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2528881%2F0ceb76a0-45ff-404f-b22a-9fd99859ed5e.png</url>
      <title>DEV Community: Akshay Chavan</title>
      <link>https://dev.to/aksh11</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aksh11"/>
    <language>en</language>
    <item>
      <title>First Thoughts on Azure vs Aws as a young dev</title>
      <dc:creator>Akshay Chavan</dc:creator>
      <pubDate>Wed, 30 Jul 2025 10:46:51 +0000</pubDate>
      <link>https://dev.to/aksh11/first-thoughts-on-azure-vs-aws-as-a-young-dev-46pb</link>
      <guid>https://dev.to/aksh11/first-thoughts-on-azure-vs-aws-as-a-young-dev-46pb</guid>
      <description>&lt;p&gt;One thing I got very frustrated with Azure was what’s the diff between Azure WebApps and Azure VMs if WebApp is underlying a VM only? I could do it myself na, like create a VM and run my container there ;)&lt;br&gt;
The answer was in, ofc, how much control and responsibility you want over the infrastructure. You can absolutely run your container on a VM (e.g., via Docker or AKS). But with App Service for Containers, you can just deploy your container image and let Azure handle the rest — no VM setup, patching, or scaling logic needed.&lt;/p&gt;

&lt;p&gt;Then I was like why are AWS lookalikes - Beanstalk or App Runner - very rarely used in AWS community?&lt;br&gt;
Coz AWS is made infra-heavy from the start, means those people preferred fine-grained control and customization (which I myself prefer, i like to be in control :P ). So something like App Service - Beanstalk feels too opinionated. So it’s like “If I’m going to manage infra, I might as well use ECS or EC2 directly.”&lt;br&gt;
On the other hand, Azure is like a PaaS-first mindset. It was built with a strong enterprise and "developer productivity focus". So people using Azure prefer to just deploy on App Services and not care about underlying infra themselves.&lt;/p&gt;




&lt;p&gt;Thanks :))&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>productivity</category>
      <category>aws</category>
      <category>azure</category>
    </item>
  </channel>
</rss>
