it’s not about picking a framework or two. It is a transformational journey and getting DevOps right
Getting to know the services of what your cloud provider has to offer, and really tuning your software to the underlying infrastructure, that is what cloud-native is basically all about. Technologies or frameworks are not going to make you cloud-native
it’s hooking stuff together, because if you want to reap the benefits of the cloud, you really have to know all the services that your cloud provider has to offer (e.g. there’s at least four or five ways to run Docker containers on AWS)
Figuring out which way actually suits that particular application or that particular component, that is what cloud-native is actually about
Gluing the software and your infrastructure together is something which is not an end state. This is a continuous journey.
It’s not thinking about servers and managing servers at scale; it is thinking about managing a mixture of both software and infrastructure at scale. It’s about services and consuming everything as API’s, and gluing that together as a deployment.
it’s about modernizing your infrastructure and the process of actually moving faster and not breaking things
The organizational culture plays a large role in it (see Conway’s Law…)