Cloud Native is About Culture, not Containers

What is the work you're doing today?

I'm a lead developer in the IBM Garage. I work with large clients and small clients. And one of the main things that we do is help clients develop cloud-native applications and take their current applications that maybe were not developed with cloud-native in mind and move them to the cloud.

What are your goals for your QCon talk?

I'm hoping to share some of the learnings that I've acquired through painful experience and maybe help people avoid some of those mistakes, but also help people reframe their thinking about the cloud to think about and cloud-native in particular, to think about it as something that isn't just a piece of software that they can buy, that there need to be changes in a whole bunch of areas in how an organization delivers software to actually truly get the benefits of cloud-native.

What do you want people to leave the talk with?

The first key takeaway is that you can't just buy Kubernetes and then be cloud-native, and you can't just split your application across 16 containers and be cloud-native. And in fact, you can't necessarily split your application across 16 containers and even have it as reliable as it was before. There's a lot of things to think about.