17 Nov
Azure Application Migration
More and more enterprises want to move their existing applications to Azure Cloud to leverage modern infrastructure but are not sure of what it takes to plan, migrate, manage and scale. We explore a wide range of considerations and migration strategies for moving to the cloud.
Moving an existing website to Microsoft’s Azure Web Apps (lift and shift) has been made easier by introduction of tools from Azure. But if you want to leverage wider benefits of Azure cloud, here are a few things to consider before you start your migration.
Azure provides a wide array of configurable security options and the ability to control them so that we can customise security to meet the requirements of your organisation’s deployments. We can work with you on an ongoing basis to access your security needs and update security configuration across operations, application and data.
.
Migration Consideration and Methodology
Environmental Consideration: Before migrating self-hosted on-premise applications to the Microsoft Azure cloud platform, we must make a decision about the model best suited for your application and organisation. Options such as Platform as a Service (PaaS) provides complete hardware and software portfolio, including the runtime environment. On the other hand, IaaS or Infrastructure as a Service (IaaS), provides just a virtualized hardware alone.
- Application and Database consideration: Before migrating on-premise application to Azure we must analyse :
- Application compatibility – Analyse if the application is architecturally fit for Microsoft Azure. Azure App Service offers popular frameworks including .NET, .NET Core, Java, Node.js, Python, PHP and Ruby.
- External/internal dependencies – Check if there are any external application dependencies which need to analysed and if those are accessible through Azure.
- Application class – Verify how the application is classified in the business. Business critical and LOB applications demand high availability and need to be provisioned accordingly.
- Application integration – checks whether the candidate application is integrated with other on-premise applications and shared services. If integration is required, then would Azure Integration Services be able to offer the required capability?
- Database compatibility – Analyse whether the existing database is best fit to migrate to Azure or which type of database is perfectly fit for our application. Azure offers different types of databases including Azure SQL Server, Cosmos DB, Table storage, GraphDB, etc.
- Application maintenance/management – Identify how the logs are maintained and where they are stored currently. These are critical for ongoing maintenance of the application.
- Compliance requirements – Check if there are enterprise compliance and regulations that govern whether data can be moved/stored outside the enterprise’s control.
- Cost – verify whether the moving application is cost-effective for the enterprise. Before migrating to the Azure cloud platform we analyse the estimated Total Cost of Ownership (TCO).
