<p>What could be the pros and cons of leveraging RabbitMQ as a PaaS service via CloudAMPQ or as Pods on AKS.</p>
<p>This is taking into consideration HA, DR scenario.</p>
<p>What factors (eg. Retention) can help make the decision?</p>

Khushaboo Shandilya
<p><strong>RabbitMQ as PaaS (CloudAMPQ)</strong></p>
<ul>
<li>First, benefit without any doubt no responsibility on your shoulder
if using PaaS.</li>
<li>Pluggable solution nothing to worry about more</li>
</ul>
<p><strong>RabbitMQ on Kubernetes</strong></p>
<ul>
<li><p>Personal experience we have been running it for a long, your monitoring should be stable, 24*7 support team or rotation-based team if anything goes wrong.</p>
</li>
<li><p>Understanding required of components how HA works</p>
</li>
<li><p>Although it's stable however depends on your application and size</p>
</li>
<li><p>Cost calculation that could affect Business at one stage, so do calculate nodes capacity and a minimum of PODs planning</p>
</li>
</ul>
<p>You can check out this helm chart using this you will be able to deploy the HA rabbitMQ on k8s: <a href="https://github.com/bitnami/charts/tree/master/bitnami/rabbitmq" rel="nofollow noreferrer">https://github.com/bitnami/charts/tree/master/bitnami/rabbitmq</a></p>
<p>i am not sure which version of RabbitMQ your app required, Ordering option required or not do checkout this basic thing also first with Dev.</p>
<p>Accordingly, you can also choose there could be chances on managed services some of version or feature like ordering won't be available.</p>
