In 2019, KPN migrated the kpn.com website to the Public Cloud. The developers completed this migration within six months. How did the engineers get this done and what was involved?
Cloud plays a critical role in digital transformation. When KPN initiated the migration of kpn.com to the Public Cloud, it was driven by several motives. Not only would this decision reduce costs, but the Public Cloud offered development teams more options and freedom to deliver the best customer experience that was no longer offered by on-premise hosting platforms. This decision also meant that every IT team would work as a DevOps team. Busra, Lead Software Engineer at KPN, was involved in this from the beginning.
Cloud migrations: what forms are there?
Before we look specifically at the migration journey that KPN has undertaken, it is good to take a brief look at the different forms of cloud migrations that a company can undertake.
The most common is to move data and applications from a local on-premises data center to the public cloud. However, cloud migration can also involve moving data and applications from one cloud platform or cloud provider to another; this is called cloud-to-cloud migration. A third form of migration is reverse cloud migration, cloud repatriation or cloud exit. With the latter, data or applications are removed from the cloud and - brought back to a local data center.
There are also intermediate forms. We speak of a hybrid cloud model when there is a combination of public and private cloud models, with data being moved between the two. And in a multi-cloud scenario, a company uses IaaS options from more than one public cloud provider.