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 day 2 operations

People in the Kubernetes community often say that deployment is day 1 and that the kinds of things you do to maintain the application afterward are day 2 operations. Some examples of day 2 operations include the following:

  • Scaling a given microservice up or down
  • Upgrading to a newer version of a microservice
  • Setting a trace string to perform problem determination

Let's look at each one of these in detail.

Scaling a microservice

One of the benefits of a microservices architecture is that you can independently scale each microservice. Rather than having to scale up all parts of a monolithic application at once, you can scale just the part that is experiencing the throughput or response time issues.

One thing to be aware of when using resources generated by an operator is that the operator itself owns those resources, and won't let you change them directly. For example, if you wanted to edit the Portfolio deployment...