At the beginning of 2019, cloud adoption was one of the key topics on top of my agenda. .This article provides in-depth commentary on how one organization migrated their critical on-prem application to AWS Cloud by re-platforming.
At the beginning of 2019, cloud adoption was one of the key topics on top of my agenda. As such, we started developing a centralized cloud strategy with the objective to use it as the foundation for governing our evolution for the next few years.
Our cloud strategy included both, the migration of our existing legacy systems as well as building new cloud-native Microservices platform.
For the migration of our existing on-premise legacy systems, we have determined what should be in our target environment and the migration strategy for each application. That brought us to adopt a combination of different approaches, in alignment with some of “The 5 R’s” that Gartner outlined in 2011.
My focus in this article is around the re-platforming approach (lift, tinker and shift)
Design. Design. Design. Migrate. Validate. Repeat. Cutover. Operate.
In summary this is how we did it and I believe this simple approach increased our chances of success.
We had few critical business applications falling under the re-platforming option, and for us there were a few candidate applications to migrate first because of what the benefits migration can bring to business in terms of availability, security, performance and other factors.
We knew that for the first migration, we have to choose the right candidate for POC and pilot testing. When we started, the rule of thumb was to choose an application that is:
However, in our case what actually happened was different. we started with the applications that were the most business-critical and which had the biggest impact on business. We realized that we had to move fast with these applications when we experienced a major data center outage and for an entire day we could not serve our users and our business partners. That is when we decided that we have to move these business-critical applications in the cloud-first and we have to move them fast.
We chose Amazon Web Services (AWS) as our cloud provider because it provided us with the greatest scale and the broadest set of services and features. I will take you through the key reasons why we chose to move to AWS cloud.
To move or not to move? Benefits are multifold when you are migrating to the cloud. Get the correct information to make your decision, with our cloud engineering expertise.
Take a look at some of the top cloud migration services you can use to migrate your services from on-premises to AWS Cloud. You need to understand the general terms of this field.
Learn AWS cloud concepts, AWS services, security, architecture under AWS cloud practitioner course from AWS certified instructors. Authorized AWS Training
Mismanagement of multi-cloud expense costs an arm and leg to business and its management has become a major pain point. Here we break down some crucial tips to take some of the management challenges off your plate and help you optimize your cloud spend.
Before dipping that first toe in the cloud migration, think of devising the transition plan. 6Rs Migration Technique has become a staple of cloud migration strategy.