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

Adding an ORM layer to our applications

If you've ever worked on an Enterprise project before, you will know that almost every Java application uses an ORM tool to map an external database. The advantages of mapping a database structure with Java objects are as follows:

  • Database neutrality: Your code will not be database-specific, so you don't need to adapt your code to a specific database SQL syntax, which may vary between vendors.
  • Developer friendly workflow: You don't need to write complex SQL structures to access your data – you simply need to refer to Java fields.

On the other hand, it's also true that, by writing native SQL statements, you can be truly aware of what your code is actually doing. Also, in most cases, you can achieve maximum performance benefits by writing direct SQL statements. For this reason, most ORM tools include an option...