Thanks for your question. In the book we have focussed on this very aspect - wherein how do you select technology stacks, cloud services, processes, and even certain open-source and ISV offerings which can help you be truly cloud-native. In fact, we have also come up with a Cloud Native Maturity Model (CNMM), which revolves around three axes:
a) Cloud Native Service Adoption
b) Application centric design patterns c) Degree of Automation
So based on the above, any workload/application that's deployed in cloud can qualify to be cloud-native, however the degree to which it's cloud native will depend on how well you are using best practices around those axes. In the book, we also talk about 12-factor application design principles which are very important in the context of being cloud-native. So net-net, there's no one technology or cloud service which if used makes you cloud-native, and rather its a combination of multiple aspects (CNMM axes, as mentioned above), which makes your workload to be much more optimal and cloud-native.
Hope this helps and makes you even more excited to read the book :-)
In terms of technology, I heard of Spring Cloud (java-based development) + Travis CI/CD + Docker + AWS, as a good combination. What do you think?
posted 9 months ago
Yes, I have heard some of the customers use that tech stack. However, I would advise you to take a look - a) Serverless technologies like AWS Lambda to reduce operational burden (b) Other cloud native services for DevOps (like Code* and Cloud9), which will make it easier to operate and even remove some of the licensing requirements.