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