This doesn’t happen overnight. It’s best to do a thorough portfolio
assessment, over four to six weeks. Look at the whole picture.
Classify the workloads based on different criteria – what can be
ported easily, what needs to be rebuilt, and what would you have
to spend to manage certain development tasks. Run this through a
Cloud Business Office function, and you will emerge with a plan
based on the business value a particular platform strategy will
deliver.
The Future
Still under the covers are serverless platforms such as Lambda or
Azure, which use container orchestrators with advanced schedul-
ers and hypervisors to pre-warm the containers and launch them
on-scale. Today, serverless poses limitations in terms of support
for multiple languages, execution periods and deployment models.
But it is just matter of time before you will be able to include the
serverless scheduler such as Virtual kubelets on top of Kuberne-
tes, to standardize the packaging and deployment models across
both serverless and container platforms.
Cloud-native computing is changing the landscape – forcing orga-
nizations to think about new models and new delivery methods.
Choosing the right platform is critical to the long-term success of
a cloud-native implementation. Settling on a strategy is the first
step. Take time to understand your options and make the decision
that is right for you.
SUMMER 2018 | THE DOPPLER | 25