Session

Common cloud migration pain paints and how to tackle them

There are different obstacles, that you’re facing when starting almost from scratch with the cloud migration of your application. They are related to architectural aspects: what about the structure, what about the components of the microservice, which has to be established in the cloud? Which services of the cloud provider should be used, e.g. serverless services or a Kubernetes service? They are related to technical issues - probably common mistakes, for example, inappropriate deployment rules of workloads, scheduling problems of Kubernetes pods, wrong or missing policy settings for pulling container images, etc. They can be referred to as financial aspects: what costs can be expected after implementing a minimum viable product or in the future by hosting a productive environment for your customer?
Which problems could be overcome by using infrastructure as code?

I’ve faced several of those issues and would like to reveal my approaches by providing explanations with regard to real implementations.

Patrick Koch

Cloud Adoption Engineer at AVL List GmbH

Graz, Austria

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top