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

Configuring cloud-native applications using MicroProfile Config

MicroProfile Config (source code located at is the first specification created by the MicroProfile community. The concept of configuration has been around for a decade. You may recall in Chapter 1, Cloud-Native Application, we briefly discussed the Twelve-Factor App, in which the third factor III. Config ( recommends that a twelve-factor app stores its configuration in an environment that is separate from the application code. This is because any configuration value update will not lead to the application code being rebuilt. But sometimes, it is not realistically possible to store all configs such as security credentials and much more in that environment. It is also common for some configuration to be stored in a database. Since the configuration could be in many different places, a mechanism for obtaining the configuration is required. Quite a...