Lift & Shift
With the Lift and Shift method, applications are usually lifted 1 to 1 into the cloud. No changes are made to the application and the architecture is not adjusted. In the simplest case, a virtual machine is exported and imported into the infrastructure of the cloud provider and operated there.
This approach is used for fast and migration, e.g. when the local data center is abolished or the hardware no longer has a support contract, etc.
The cost savings achieved here are rather small and the scaling is done vertically, and the advantages of a cloud cannot be fully utilized.
Replatforming the application
Applications similar to the Lift & Shift principle are lifted into the cloud. Optimizations are performed to take advantage of the cloud. However, the basic architecture of the application is not changed.
An example could be that you can use existing cloud services (e.g. AWS RDS), the Managed Database Service for relational databases, reducing operating costs and increasing system availability and performance. You no longer have to worry about the administration and availability of the database.
Containerization of existing applications
By using containers, it is possible to break down complex monolith applications and pack them in a container in layers. The use of containers is the perfect basis to be able to get all the advantages of the cloud after migration and the basis for a flexible application environment.
The use of containers and the use of the corresponding AWS services Fargate or EKS eliminates the infrastructure management. I.e. you can focus on building and operating your application to optimize the software deployment process.
Secure mobile work—home in the home office or on the go—with a virtual desktop directly from the cloud.