Rebuild
The rebuild strategy involves putting aside the old application and building the same functionality from scratch using the Azure Platform as a Service (PaaS) capabilities. Leverage services like Azure Functions and Logic Apps to build the application tier, and use Azure SQL Database or other hosted Azure data services for the data layer.
This is the most intrusive process, as you will be starting from scratch with your application and this by far includes the most business commitment. You will be gathering new requirements and possibly changing the flow of the application
because the application is no longer supportable in its current condition.
Rebuilding is the preferred option when:
The application is past its lifespan or its functionality relies on some outdated third-party resource that does not have a cloud solution.
You want to build new applications using cloud-native technologies.
Adding new functionality or building innovative apps that take advantage of advancements in artificial intelligence (AI), blockchain, and Internet of Things (IoT).
When you want to apply innovative DevOps practices.
Have few dependencies on other business processes.
Rebuilding will help you leverage all the new Azure components and take advantage or the features Azure PaaS and SaaS solutions provide. This approach provides businesses to manage their applications while Azure manages everything else.
The pros of this approach are:
Most cost effective option
No complexity of managing software licenses.
No dependency on middleware or existing infrastructure.
The cons of this approach are:
Its hard to get the same level of functionality as in the custom-built app.
You need to adopt patterns like eventual-consistency with rebuild option.
Advance and detailed planning is required to figure out which parts of the application can be rebuilt in to Azure and which cannot.
References:
Comentarios