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

Cloud-native application transactions

Cloud-native application transactions try to ensure data consistency and integrity, similar to a traditional transaction. Traditional transactions normally use the two-phase commit or XA protocol. The two-phase commit protocol ensures that transactional updates are committed in all databases or are fully rolled back in the case of a failure. It is widely supported by many databases. As its name implies, this protocol consists of two phases: the voting phase and the commit phase. In the voting phase, the transaction manager gets approval or rejection from the participating XA resources. In the commit phase, the transaction manager informs the participants about the result. If the result is positive, the entire transaction will be committed. Otherwise, it will be rolled back. This protocol is very reliable and guarantees data consistency. The drawback is that it locks resources and might lead to indefinite blocking. Therefore, it is not suitable...