OpenShift for Developers, 2nd Edition

Chapter 6. Developing and Deploying from Source Code

Now that your local OpenShift has OpenShift Pipelines installed, you’re ready to deploy a multitier application. This app is more complex than your initial “Hello World” service from Chapter 4, as it has two components that need to communicate. The app also has been designed to eventually incorporate a database, as you will see in Chapter 7. You will hand some of these complexities off to a pipeline to automate some of the repetitive tasks of building and rebuilding the application through several iterations.

Noted: A Cloud-Ready Notes Application

Noted is a simple note board where each note contains a title and some content. When an optional database is connected, it will allow you to maintain the list of prior posts and delete them. It consists of two main components, a frontend and a backend, similar to how a typical web application might be architected.

The frontend is written in Node.js and uses the React library to display the list of posts. The posts call the quarkus-backend REST endpoint at /posts. While you will not be editing the frontend component of the app, you can find the source code for the frontend app on GitHub.

The backend is written using Quarkus, a Kubernetes-native Java stack for microservices and serverless development with fast startup times, hot reloads, a small memory footprint, and compact applications. The backend provides the /posts REST endpoint to the frontend app. Right now the lists of posts ...