You're reading from Practical Cloud-Native Java Development with MicroProfile Develop and deploy scalable, resilient, and reactive cloud-native applications using MicroProfile 4.1

Product type Paperback

Published in Sep 2021

Publisher Packt

ISBN-13 9781801078801

Length 404 pages

Edition 1st Edition

Languages

Java

Tools

Microprofile

Concepts

Cloud Native

Authors (5):

Alasdair Nottingham

John Alcorn

David Chan

Emily Jiang

Andrew McCright

+1 more

View More author details

Table of Contents (18) Chapters

Preface

1. Section 1: Cloud-Native Applications

2. Chapter 1: Cloud-Native Applications FREE CHAPTER

3. Chapter 2: How Does MicroProfile Fit into Cloud-Native Application Development?

4. Chapter 3: Introducing the IBM Stock Trader Cloud-Native Application

5. Section 2: MicroProfile 4.1 Deep Dive

6. Chapter 4: Developing Cloud-Native Applications

7. Chapter 5: Enhancing Cloud-Native Applications

8. Chapter 6: Observing and Monitoring Cloud-Native Applications

9. Chapter 7: MicroProfile Ecosystem with Open Liberty, Docker, and Kubernetes

10. Section 3: End-to-End Project Using MicroProfile

11. Chapter 8: Building and Testing Your Cloud-Native Application

12. Chapter 9: Deployment and Day 2 Operations

13. Section 4: MicroProfile Standalone Specifications and the Future

14. Chapter 10: Reactive Cloud-Native Applications

15. Chapter 11: MicroProfile GraphQL

16. Chapter 12: MicroProfile LRA and the Future of MicroProfile

17. Other Books You May Enjoy

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...