Book Image

Hands-On Cloud-Native Applications with Java and Quarkus

By : Francesco Marchioni
Book Image

Hands-On Cloud-Native Applications with Java and Quarkus

By: Francesco Marchioni

Overview of this book

Quarkus is a new Kubernetes-native framework that allows Java developers to combine the power of containers, microservices, and cloud-native to build reliable applications. The book is a development guide that will teach you how to build Java-native applications using Quarkus and GraalVM. We start by learning about the basic concepts of a cloud-native application and its advantages over standard enterprise applications. Then we will quickly move on to application development, by installing the tooling required to build our first application on Quarkus. Next, we’ll learn how to create a container-native image of our application and execute it in a Platform-as-a-Service environment such as Minishift. Later, we will build a complete real-world application that will use REST and the Contexts and Dependency injection stack with a web frontend. We will also learn how to add database persistence to our application using PostgreSQL. We will learn how to work with various APIs available to?Quarkus?such as Camel, Eclipse MicroProfile, and Spring DI. Towards the end, we will learn advanced development techniques such as securing applications, application configuration, and working with non-blocking programming models using Vert.x. By the end of this book, you will be proficient with all the components of Quarkus and develop-blazing fast applications leveraging modern technology infrastructure.
Table of Contents (15 chapters)
Free Chapter
Section 1: Getting Started with Quarkus
Section 2: Building Applications with Quarkus
Section 3: Advanced Development Tactics

The Eclipse MicroProfile Fault Tolerance API

The Fault Tolerance specification is a fundamental API that can be used to handle the unavailability of your microservices by endorsing a set of policies that can improve the resiliency of your applications. The following fault tolerance policies are available:

  • Timeout: Defines a timeout for the execution of a service call
  • Fallback: Provides a contingency solution when a failure occurs
  • Retry: Allows you to retry execution based on criteria
  • Bulkhead: Isolates partial service failures while the rest of the system can still work
  • Circuit Breaker: Defines criteria for automatic fast-fails to prevent system degradation caused by overloading
  • Asynchronous: Allows us to invoke an operation asynchronously

Let's look at these concepts in practice by using the Chapter06/fault-tolerance example. First off, in order to use the fault-tolerance...