Microsoft: Designing and moving applications to cloud
When working with customers we often come across the discussion on how one should plan on moving their line of business applications. Firstly, an enterprise needs to find the list of applications they are currently using which would then go to cloud. There are four types of applications,
- Applications which can be moved easily: now most of the cases this is lift and shift, so customer can move the Virtual Machines to the cloud and start using the application as is without much effort. This type of applications are generally of the kind which has less budget for migration or does not have enough time left to do so.
- Applications which need code change to be able to move to cloud: this is a typical application modernization where the customer not only moves their application to the cloud but leverages the power of cloud. This requires basic design change for obvious reason. Earlier when this application was designed cloud was never a requirement. So, those missing parts can be helpful in long run. Platform as a Service(PaaS) based applications can go through this model. This effort demands more budget and time. So, the applications which has less user base and low impact can be chosen for the drive. By doing this, enterprise will gain the knowledge and expertise to do plan the further migration or modernization projects. First of this kind within an organization can be considered as lighthouse application in modernization.
- Applications which does not have much lifetime left: By moving many applications to the cloud enterprise gets little extra space in the on-premises datacenter. Thus, applications which are in verge of deathbed and does not have any future roadmap can live happily in the datacenter for the time being. No one sees any value of altering them.
- Greenfield application: completely new for the organization
After IT decides the applications to work on and put them in right bucket we need a team. One team may not be helpful as this requires various kinds of expertise. Right from domain expertise to cloud knowledge. People who have developed and supported the legacy applications may have the right domain expertise but they may lack the knowledge on cloud. So, we need an advisory board who can help team decide the right approach. This purely comes from the experience and the changing landscape of cloud does require constant touch on what is happening around to leverage the latest and greatest technologies.
Read the entire article here, Designing and moving applications to cloud
via the fine folks at Microsoft