Green Cargo Drives Incremental Cloud Migration on OutSystems
Learn how eco-friendly rail logistics company Green Cargo has rediscovered its innovation mojo, delivering digital innovation up to 10x faster with OutSystems.
Cloud migration is the process of moving applications, services, databases, and other IT resources to the cloud. That move can happen from on-premises infrastructure to the cloud, or from one cloud to another.
With the pressure to deliver innovative products and services at an all-time high, companies are being forced to cut the shackles from their outdated technology and processes and modernize their legacy systems. To reap the benefits from cloud applications, such as flexibility, resilience, agility, and open new opportunities for the business, organizations move parts or their entire IT resources to the cloud.
The main reason organizations migrate to the cloud is to increase competitiveness and their ability to outflank their competitors. They’re able to do so by reaping the benefits cloud infrastructures offer, which we discussed in greater detail in the previous cloud computing and cloud-native sections:
Migrating to the cloud can be done through different approaches. These are also known as the “6 R’s” of cloud migration.
Also known as “lift and shift” where you grab your on-premises environment (or cloud if you’re moving between clouds) as it is and move it to the cloud without making any major change.
Similar to a “lift and shift” approach, but you make a few adjustments to your environment to better adapt to the cloud. Just like in a rehosting approach, you don’t change your app's architecture.
You move your apps to a new cloud-based platform. It’s a less conservative approach when compared to rehosting and re-platforming because you lose your existing licensing and code, which means you need to retrain your developers to use the new platform.
You rebuild your existing applications. This approach is mostly used when an organization wants to add cloud capabilities to their apps, and they’re not available in their existing environment. It’s usually more expensive than the approaches already mentioned, but it is also more future-proof.
After you access your app portfolio, and identify what needs to be moved to the cloud, there are a few apps that might no longer be useful. So you basically retire them and keep your house clean.
Not every application should be migrated to the cloud. Maybe for security or compliance reasons, some apps make more sense to stay on-premises. In a retaining model, you create a hybrid infrastructure, where a few resources are in the cloud, and others stay on-premises.