In previous posts we’ve discussed the significant market share gap between top dog Amazon Web Services and its closest competitor, Microsoft Azure. We’ve talked a bit about why engineering skews toward AWS while IT tends to prefer Microsoft Azure. Still, all things being equal, is one of these two cloud platforms “better” than the other?
Objectively Comparing Amazon and Microsoft
Consider the matter objectively, without resorting immediately to what one offers and the other doesn’t in the abstract. Instead, think of the matter in terms of what your organization needs. For example, if you’re building an application, look at what your application requires and which cloud platform best meshes with the features you need. How much code would you have to change to get your application going on each? This can help you arrive at a more utilitarian solution than simply considering subjective comfort.
Support for AWS
Support is another is another issue. AWS requires you to purchase an additional support package to receive first year support directly from Amazon. Otherwise, you’re relying upon your in-house IT team or searching the Internet yourself. On the other hand, Azure offers robust first-year support, as well as an engaged online community.
Some organizations reject Azure entirely without consideration because they run on Linux shells. However, there’s solid support for Azure run on Linux shells. Nor are the price differences between the two insignificant. While it’s true that cloud costs are falling dramatically, cost difference can be significant, especially when dealing with applications. Look at what each will actually for you to get a sense of what you’re looking at paying.
Next time we will explore more closely the relationship engineering departments have with AWS.