We do, and we&#x27;re going into Azure native tech (Reliable Actors&#x2F;Services). Azure tech is designed to overcome one of the major limitations of the cloud, which is:<p>&gt; bad stability problems<p>The cloud is inherently unstable. If you have this problem it means that your architecture isn&#x27;t ready for the cloud. This is why software developers are interested in consensus&#x2F;fault-tolerance in the first place. Azure might be <i>more</i> unstable but at the end of the day the degree of stability is completely moot. If your software isn&#x27;t designed for the cloud bad things will eventually happen. It doesn&#x27;t matter if it takes hours, minutes, or days.<p>That is the reason we chose Azure: Reliable Actors&#x2F;Services are a huge boon when it comes to writing software that <i>correctly</i> deals with cloud conditions because they are architectural patterns that are built for it.<p>This is why Netflix uses chaos monkey[1]. Even the Azure SDK ships with a chaos monkey script. If fault tolerance is not a concern of yours then cloud should be your very last concern. We tried slapping on-premise architecture on the cloud (evaluating AWS, RackSpace and Azure) and we had some degree of stability problems across all of them.<p>[1]: <a href="http:&#x2F;&#x2F;whatis.techtarget.com&#x2F;definition&#x2F;Chaos-Monkey" rel="nofollow">http:&#x2F;&#x2F;whatis.techtarget.com&#x2F;definition&#x2F;Chaos-Monkey</a>