Since you are already on the Cloud, you should be aware of what can be accomplished on-premise and what is possible on cloud, be it Amazon Web Services (AWS) or Microsoft Azure.
When you plan to migrate between AWS to Azure or vice-versa, it is imperative that you understand what each has to offer and make an informed decision accordingly. Understand where the similarities end and what you need to brace yourselves for.
Availability Model & how your application has been developed
Both AWS and Azure have quite a few similarities. Microsoft Azure has resources available online that list the equivalent services in Azure, to those available in AWS.
When moving an application to AWS or Azure, you need to understand how it has been developed. The difference in the availability model of AWS and Azure is critical to your decision. AWS is based on availability zones, to manage uptime of applications and their components. Azure is based on availability at two levels – locally via availability sets and geographically through regions.
Platform of your application
What your target cloud architecture will look like, should be based on your understanding of the integration points your application has and the SLAs it must meet. It is also key to take into consideration the underlying platform services in use. In case you are re-platforming your application, you need to review your existing deployment processes. In this, Azure has an edge, with its ability to leverage features available for modern Continuous Deployment (CD) scenarios.
In the present data driven landscape, how you handle data during the migration between AWS and Azure is of utmost importance. You need to decide if you want to leave it where it is, migrate via physical shipping or migrate via logical transfer. You also need to decide how much data you will transfer and what, if any, and its impact on existing network services.
AWS groups its Infrastructure as a Service offerings into the four categories of Compute, Storage and Content Delivery, Database, and Networking. It has management tools like Amazon CloudWatch, AWS Cloudtrail for tracking user activity and API usage, and AWS Config to monitor infrastructure resource usage. Azure uses the nomenclature of Compute, Data Management (which includes database) and Performance, and Networking. It has a number of services and integrations for in-depth monitoring and alerting on infrastructure performance metrics and logs.
Ease of licensing
The simplicity of licensing is a component that also plays a big role in the decision regarding the move to AWS or Azure. Azure offers license mobility. It is important that you find out if your application is eligible for license mobility. Also keep in mind that Windows Server itself is not eligible for license mobility.
Microsoft allows seamless hybrid cloud interaction with platforms like Azure StorSimple, Hybrid SQL Server, Azure Stack and others. Amazon offers a few hybrid solutions like Storage Gateway, DynamoDB Local, and OpsWorks. For now, Microsoft has an upper hand.
In the Open Source cloud hosting space, Amazon AWS has a significant lead over Azure. AWS has been Linux-friendly from the start. Amazon’s upper hand with open source can be attributed to its long association with open source. Azure does work much more seamlessly with Microsoft development tools than without them. Azure and Microsoft, are trying to embrace open source in a big way. The gap in this regard is fast closing.
It would mostly depend on user behavior. Both AWS and Azure provide cost calculators that you can use to get a better understanding of what it would cost.
NetEnrich will help you through the various tough decisions you may need to take, to limit downtime and make the most of either an AWS or Azure investment, as quickly and effectively as possible.