Book Image

Hands-On Cloud Development with WildFly

By : Tomasz Adamski
Book Image

Hands-On Cloud Development with WildFly

By: Tomasz Adamski

Overview of this book

The book starts by introducing you to WildFly Swarm—a tool that allows you to create runnable microservices from Java EE components. You’ll learn the basics of Swarm operation—creating microservices containing only the parts of enterprise runtime needed in a specific case. Later, you’ll learn how to configure and test those services. In order to deploy our services in the cloud, we’ll use OpenShift. You’ll get to know basic information on its architecture, features, and relationship to Docker and Kubernetes. Later, you’ll learn how to deploy and configure your services to run in the OpenShift cloud. In the last part of the book, you’ll see how to make your application production-ready. You’ll find out how to configure continuous integration for your services using Jenkins, make your application resistant to network failures using Hystrix, and how to secure them using Keycloak. By the end of the book, you’ll have a functional example application and will have practical knowledge of Java EE cloud development that can be used as a reference in your other projects.
Table of Contents (14 chapters)

Pipeline build

In the first chapter, when we were explaining why you may be considering implementing the microservice architecture in your applications, we mentioned the challenges that are being currently faced by application developers and architects.

One of the key tools that may enable us to deal with providing software in a way that enables us to meet those challenges is automation. As we covered in the preceding chapter, OpenShift enables us to automate infrastructure provisioning. However, we need more than that.

We will also like to automate the process of deploying software into production. Ideally, we will like to have tools that will enable us to release software immediately. OpenShift provides such a tool in the form of the build pipeline. Let's introduce the rationale behind this concept.

Let's start with CI.