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

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

Using MicroProfile Context Propagation to manage context

MicroProfile Context Propagation (https://download.eclipse.org/microprofile/microprofile-context-propagation-1.2/) defines a mechanism for propagating context from the current thread to a new thread. The types of context include the following:

Application: This normally includes the thread context class loader as well as java:comp, java:module, and java:app.
CDI: The scope of the CDI context, such as SessionScoped and ConversationScoped, is still active in the new unit of work, such as a new CompeletionStage.
Security: This includes the credentials that are associated with the current thread.
Transaction: This is the active transaction scope that is associated with the current thread. This context is not normally expected to be propagated, but cleared instead.