Migrating a monolith to Cloud-Native and the stumbling blocks that you don’t know about

So your company has finally decided to move to the Cloud Native ecosystem. You’ve landed on containerization as your first step. You heard that all you needed to do was containerize your first app and then push it to Kubernetes/OpenShift/Nomad, and the cost savings just come. You’ve done this, and well, things have gone not as planned. Some of the tech didn’t do what you expected, and wait, what do you mean our OpEx has gone up?

Simply said: the promise of containerization or migrating to the Cloud Native ecosystem can be a lie if you don’t do your homework. Sadly most companies don’t. In this talk, I’ll explain a few gotchas that a “few” enterprises, in the guise of AsgharLabs, hit moving towards the Cloud Native world, and hopefully, you’ll learn from their mistakes, so you’re trip down this path will be more comfortable and closer to the promise.

  • Outline
  • Introductions
  • What is AsgharLabs and where they started, what they thought they needed to do
  • Where I came into the conversation to help AsgharLabs
  • Questions you should ask after getting your app containerized
  • Where are the architectural advantages and disadvantages?
  • Are we doubling up on things?
  • Isn’t automation good here? Why is this thing so complicated now?
  • Questions you should ask about the cultural shift that will happen
  • How the economics of the Cloud can differ from your Datacenter
  • What do you mean our support is now Stack Overflow?
  • What do you mean our goal is to move away from the CCB?
  • Some tangible things you can start with to help become more successful
  • Build that pipeline extension
  • Collaborate with other teams
  • Visibility and Monitoring
  • Conclusion and where you can go from here



JJ Asghar

Developer Advocate for the IBM cloud

JJ works as a Developer Advocate representing the IBM Cloud all over the world. He mainly focuses on the IBM Kubernetes Service and OpenShift trying to make