Book Image

Practical Cloud-Native Java Development with MicroProfile

By : Emily Jiang, Andrew McCright, John Alcorn, David Chan, Alasdair Nottingham
Book Image

Practical Cloud-Native Java Development with MicroProfile

By: Emily Jiang, Andrew McCright, John Alcorn, David Chan, Alasdair Nottingham

Overview of this book

In this cloud-native era, most applications are deployed in a cloud environment that is public, private, or a combination of both. To ensure that your application performs well in the cloud, you need to build an application that is cloud native. MicroProfile is one of the most popular frameworks for building cloud-native applications, and fits well with Kubernetes. As an open standard technology, MicroProfile helps improve application portability across all of MicroProfile's implementations. Practical Cloud-Native Java Development with MicroProfile is a comprehensive guide that helps you explore the advanced features and use cases of a variety of Jakarta and MicroProfile specifications. You'll start by learning how to develop a real-world stock trader application, and then move on to enhancing the application and adding day-2 operation considerations. You'll gradually advance to packaging and deploying the application. The book demonstrates the complete process of development through to deployment and concludes by showing you how to monitor the application's performance in the cloud. By the end of this book, you will master MicroProfile's latest features and be able to build fast and efficient cloud-native applications.
Table of Contents (18 chapters)
Section 1: Cloud-Native Applications
Section 2: MicroProfile 4.1 Deep Dive
Section 3: End-to-End Project Using MicroProfile
Section 4: MicroProfile Standalone Specifications and the Future

Using MicroProfile features in Stock Trader

Let's start with a view of which Stock Trader microservices use which MicroProfile features. Note that there are two ways a microservice can benefit from a given MicroProfile feature – implicitly or explicitly:

  • In the implicit case, just listing the feature in your server.xml file gives you value; for example, you can obtain default implementations for readiness and liveness probes just by enabling the mpHealth-3.1 feature.
  • In the explicit case, you directly code to the APIs offered by the feature, such as implementing your own custom logic for whether your microservice is healthy by coding to classes in the package from within your own Java classes.

In the following table, we can see which microservices use which feature, with the not sign meaning not at all, the dash meaning implicit usage, and the checkmark meaning explicit usage:

Table 8.1 – MicroProfile...