Microsoft has done an amazing job building out the services available in Azure. They are simultaneously broad and deep, and expanding rapidly. My job is to help EMC’s presales engineering community make sense of how Microsoft and EMC interact (both in the market and technically). I’ve struggled over the last year to do so, given the breadth of Azure offerings. So I’ve put together what I’m called an Azure Services taxonomy to help us (and our customers) understand how Azure fits into their technology landscape.
I used a Venn diagram, with Management and IaaS, Data Services, Web/Mobile and Internet of Things, and finally Network.
This is not perfect, but I think a decent start. I’ve probably missed some services, and quite certain that some of the services are misplaced. Perhaps even the major categories of the taxonomy are a bit off.
What do you think, and what would you change? Feel free to comment below, and if you’re interested in grabbing the source for this Venn, drop a comment as well.
Recent Comments