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)

API gateway

The API gateway is a service that's responsible for routing requests from clients to applications, and is very similar to a design pattern called facade, from object-oriented design, which is best described in the book Java EE 8 Design Patterns and Best Practices.

The API gateway encapsulates logic to call the proper backend services. As it is the single entry point, it can also have other capabilities such as securing services, transforming payloads, monitoring, throttling, caching, and rating the number of requests per service, and so on. The API gateway is also responsible for exposing services with different protocols.

Another scenario in which it can be used is to call multiple services, aggregate the result, and return the proper output (API composition implementation) as shown in the following diagram: