For the last few years the terms cloud-native and microservice architecture have been used interchangeably. However recently people have ceased to view microservices as the go-to solution for all problems, reflecting a growing maturity in our understanding of how to best take advantage of the benefits of cloud computing.
While microservices have many benefits, they also bring their own challenges and better understanding (and some failed microservices projects) have led to a more critical evaluation of suitability of microservices to all problems. This evolved understanding has resulted in a new interest in the place for monoliths in the cloud. Whether referred to as macroservices, or cloud-native monoliths there is a gap forming between the terms cloud-native and microservices that wasn’t there before.
What does this gap mean? How are cloud architectures evolving? How does Eclipse, through Jakarta EE and Eclipse MicroProfile, fit into this new world? Join me as I look at microservices and monoliths in the context of cloud-native architectures.