As enterprise IT teams, leadership and business owners continuously drive towards service improvements, they invariably look at the public cloud infrastructure as a possible target for their mission critical applications. Whereas virtualization is now generally accepted as the default platform for enterprise-grade applications, businesses looking to leverage the public cloud for most of these applications are still constrained in their ability to do so.
These constraints can be directly attributed to the following (among others):
- Performance Concerns – is the target public cloud robust enough to meet the application’s scale and performance requirements?
- Vendor Support – is the target cloud platform certified for the application? Will the vendor provide the necessary technical support and assistance when (not if) the enterprise requires it?
- Level of Effort – mission critical applications demand considerable attention to configuration and other considerations beyond those required for lower-tiered applications and moving from one hosting platform to another may not be a simple or quick undertaking.
This article will address two of these constraints in relations to enterprises’ desire to operate their Microsoft Exchange Server workloads on the VMware Cloud on AWS platform – Performance and Support. Part II of this article will address the “Level of Effort” aspect – we feel that this deserves a stand-alone article of its own.
Microsoft Exchange Server is one of the most prevalent Messaging and Collaboration applications in enterprises today. Microsoft officially supports virtualizing Microsoft Exchange Server (hereafter simply referred to as “Exchange” or “Exchange Server”) on the VMware vSphere virtualization platform. Because VMware has been supporting (and providing guidance for) the virtualization of Exchange Server for more than 10 years (even before official Microsoft support), virtualizing Exchange Server on the vSphere platform has become quite mainstream. Continue reading