<?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: Mihir Dudhatra</title>
    <description>The latest articles on DEV Community by Mihir Dudhatra (@mihirdudhatra).</description>
    <link>https://dev.to/mihirdudhatra</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%2F1415985%2F008d047b-1d56-46ad-91b1-0f66b19384f7.jpg</url>
      <title>DEV Community: Mihir Dudhatra</title>
      <link>https://dev.to/mihirdudhatra</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mihirdudhatra"/>
    <language>en</language>
    <item>
      <title>🐇💬 RabbitMQ: EC2 vs Amazon MQ — Why We Switched</title>
      <dc:creator>Mihir Dudhatra</dc:creator>
      <pubDate>Thu, 17 Apr 2025 11:30:12 +0000</pubDate>
      <link>https://dev.to/mihirdudhatra/rabbitmq-ec2-vs-amazon-mq-why-we-switched-ci</link>
      <guid>https://dev.to/mihirdudhatra/rabbitmq-ec2-vs-amazon-mq-why-we-switched-ci</guid>
      <description>&lt;p&gt;We had to decide between using Amazon MQ (fully managed) vs. hosting RabbitMQ on EC2.&lt;br&gt;
Amazon MQ is great:&lt;br&gt;
 ✅ Managed&lt;br&gt;
 ✅ Secure&lt;br&gt;
 ✅ No setup headaches&lt;br&gt;
But… we ran into issues like:&lt;br&gt;
 ❌ Maintenance windows that delayed recovery&lt;br&gt;
 ❌ Lost in-flight messages and interrupted background tasks&lt;br&gt;
 ❌ Less flexibility for tuning and updates&lt;br&gt;
So, we moved RabbitMQ to EC2. Now we get:&lt;br&gt;
 🔧 Full control&lt;br&gt;
 🚀 Faster recovery&lt;br&gt;
 💸 Lower cost for dev/test&lt;br&gt;
 ⚙️ Freedom to tweak everything&lt;br&gt;
Managed services are great, but sometimes you need the steering wheel. 🛠️&lt;br&gt;
🤔 Have you dealt with broker downtime or message loss during managed maintenance? What path did you take?&lt;/p&gt;

</description>
      <category>aws</category>
      <category>cloud</category>
      <category>discuss</category>
      <category>pubsub</category>
    </item>
  </channel>
</rss>
