Erdenezaya Batnasan's Key Ideas from Cloud Native Transformation
by Michelle Gienow, Jamie Dobson, Pini Reznik

Cloud-native organizations are built to take optimum advantage of functioning in cloud technologies; the cloud of course will continue to evolve and will look quite different in the future, but we also build to anticipate this. Applications are built and deployed rapidly by small, dedicated feature teams made up of developers who also know how to build in networking, security, and all other necessities so all parts of the distributed system become part of the application. This highly automated platform uses an orchestrator like Kubernetes to manage the complexity.

We call it a cloud-native transformation because, to make a successful, effective, and above all worthwhile migration, the entire organization, not just the tech stack, must change. This means evolving nontechnical aspects such as management practices, org structure, and team responsibilities, even your fundamental delivery processes to work in your new cloud-native context. Otherwise, if you simply layer the latest tech on top of the same old way you have always done things, you'll create whole new problems, including slow delivery, reduced quality, and difficulties in both project and team