Component Details
The Quarkus Coffeeshop Store Chart
This chart is responsible for deploying the applications, services and routes for the Quarkus Coffeeshop demo. It models a set of microservices that would make sense for a coffeeshop retail operation. The detail of what the microservices do is here.
Serves as the “front end” for ordering food and drinks.
The counter service receives the orders, persists them in the database, and notifies when they are ready.
The barista service is responsible for preparing items from the “drink” side of the menu.
The kitchen service is responsible for preparing items from the “food” side of the menu.
The customerloyalty service is responsible for generating customer loyalty events, when a customer enters the “rewards” email. This data is not persisted or tracked anywhere.
The inventory service is responsible for tracking food and drink inventory.
The customermocker can be used to generate test traffic.
The “majestic monolith” builds all the apps into a single bundle, to simplify the process of deploying this app on single node systems.
All the components look like this in ArgoCD when deployed:
The chart is designed such that the same chart can be deployed in the hub cluster as the “production” store, the “demo” or TEST store, and on a remote cluster.
The Quarkus Coffeeshop Database Chart
This installs a database instance suitable for use in the Retail pattern. It uses the Crunchy PostgreSQL Operator to provide PostgreSQL services, which includes high availability and backup services by default, and other features available.
Like the store chart, the Database chart can be deployed in the same different scenarios.
In ArgoCD, it looks like this:
The Quarkus Coffeeshop Kafka Chart
This chart installs Kafka for use in the Retail pattern. It uses the Red Hat AMQ Streams operator.
The Quarkus Coffeeshop Pipelines Chart
The pipelines chart defines build pipelines using the Red Hat OpenShift Pipelines Operator (tektoncd). Pipelines are provided for all of the application images that ship with the pattern; the pipelines all build the app from source, deploy them to the “demo” namespace, and push them to the configured image registry.
Like the store and database charts, the kafka chart supports all three modes of deployment.
The Quarkus Coffeeshop Landing Page Chart
The Landing Page chart builds the page that presents the links for the demos in the pattern.
