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

Managing the Reactive SQL Client

The Reactive SQL Client is an API that allows you to use reactive and non-blocking features of Vert.x to access a relational database. This brings some changes in terms of how you access your data. Let's put the costs and benefits on the table:

  • On one side, you will need to use SQL statements to enable your RDBMS to access data, instead of the abstract HQL. Also, automatic mapping between Java classes and DB is not available anymore since Hibernate is out of the game here.
  • On the other hand, you will be able to use a fully event-driven, non-blocking, lightweight alternative to stream the result of your SQL statements.

Based on your requirements, you may stick with Hibernate's API or switch to Reactive's SQL Client. Let's say you're brave and want to switch to Reactive SQL. To do that, you will need to configure your application...