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

Understanding the role of operators

Before diving into the specifics of the IBM Stock Trader operator, let's step back for a bit and consider what operators do and why they are a good thing. To do so, it's important to recall from Chapter 7, MicroProfile Ecosystem with Open Liberty, Docker, and Kubernetes, that Kubernetes defines a model where there are several built-in object types, such as Deployments, Services, Ingresses, ConfigMaps, and Secrets. In the true object-oriented philosophy, such objects not only have data but have behavior; it is the operators' job to participate in and guide the full Create, Retrieve, Update, and Delete (CRUD) life cycle of the objects they manage.

One key point is that Kubernetes not only has its built-in objects, but also has an extensibility model where vendors can add to that vocabulary, defining additional types of objects and how they should act in the Kubernetes environment. Kubernetes calls this a CustomResourceDefinition ...