Book Image

Hands-On Cloud-Native Microservices with Jakarta EE

By : Luigi Fugaro, Mauro Vocale
Book Image

Hands-On Cloud-Native Microservices with Jakarta EE

By: Luigi Fugaro, Mauro Vocale

Overview of this book

Businesses today are evolving rapidly, and developers now face the challenge of building applications that are resilient, flexible, and native to the cloud. To achieve this, you'll need to be aware of the environment, tools, and resources that you're coding against. The book will begin by introducing you to cloud-native architecture and simplifying the major concepts. You'll learn to build microservices in Jakarta EE using MicroProfile with Thorntail and Narayana LRA. You'll then delve into cloud-native application x-rays, understanding the MicroProfile specification and the implementation/testing of microservices. As you progress further, you'll focus on continuous integration and continuous delivery, in addition to learning how to dockerize your services. You'll also cover concepts and techniques relating to security, monitoring, and troubleshooting problems that might occur with applications after you've written them. By the end of this book, you will be equipped with the skills you need to build highly resilient applications using cloud-native microservice architecture.
Table of Contents (14 chapters)

Decomposition

Decomposition isn't really the best of words—it recalls something going bad. However, in this context, it means to split apart a service, such as our football manager application; that is, splitting it into different microservices and decoupling components that follow the Single Responsibility Principle (SRP). The SRP relies on the fact that one component does one and one thing only, and that it does very well. The following diagram gives us an idea about decomposition:

In our example, the overall application could have been designed and deployed as a monolith, where we group all of the pieces together. Of course, it would have worked well, but with a lot of drawbacks (flexibility, scalability, failure, elasticity, and so on).

How do you decompose an application...