Technology is all around. Invisible compute is helping us in our daily lives to improve accessibility to any kind of service: reading the news, setting the temperature in your home, planning a trip, watching series, charging your car and even read about what is going on at your kids’ school. Everything is accessible online, can be consumed in a pay per use model and is really easily accessible: an email address and online payment method is enough.
What impact does this trend have on a Cloud Service Provider (CSP)? How can one cope with these developments? And how can a CSP keep up with the competition? My answer: knowledge, innovation and the guts to challenge te status quo. CSP’s serving Independent Software Vendoers (ISV’s) are serving customers in a world where a lot of evolution is going on: applications need to be transformed from (in the worst case) monolithic architecture to a scalable, segmented stack, where development can really speed up the process of releasing new features.
In this global IT transformation, a CSP has a crucial role to play as an expert cloud partner for its customers. The transformation then can be achieved via a number of ways, transformation routes.
Transformation routes are based on the way a workload can be transformed to (public) Cloud, based on the theory of the (5) R’s:
- Relocate: move on premises workload out of the privately owned datacenters and move it to the (Public) Cloud. A relatively simple exercise, where at least datacenter IT can be transformed from an Capex to an Opex model.
- Rehost: a way of moving a locally hosted workload (server, virtual server or appliance) to a (Public) Cloud offering.
- Replatform: this is where it gets more complex. A translation is needed for the workloads hosting an application: from server to service. Think of a translation of hosted loadbalancer to aan ALB service in Amazon Web Services. Think of a local database server (Oracle, SQL) to a Aurora Database Services. This complexity is challenging, but also the most satisfying. Adapting new technology and making the application cloud-native is the deliverable in this case.
- Refactor: using cloud-native services most of the time requires a refactoring of the application. This requires interaction with the application owner, or even the developer. In combination with Replatforming the most improvement can be gained from this.
- Repurchase: acquiring a new as a Service online application, where the legacy application is being retired; not a route where a CSP can have an active role in.
A good CSP can help in all of the above digital transformation routes. The best route needs to fit in the customers company strategy, and if it comes to transforming the expense model of the local datacenter in a pay per use model, the CSP should be offering more options in a private cloud or public cloud solution.
If you would like to know how your Cloud Strategy can be translated to a solid plan, based on a fitting transformation route? Do not hesitate to contact me!