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.
quarkuscoffeeshop-web - Serves as the
front endfor ordering food and drinks.quarkuscoffeeshop-counter - The counter service receives the orders, persists them in the database, and notifies when they are ready.
quarkuscoffeeshop-barista - The barista service is responsible for preparing items from the
drinkside of the menu.quarkuscoffeeshop-kitchen- The kitchen service is responsible for preparing items from the
foodside of the menu.quarkuscoffeeshop-customerloyalty - The customerloyalty service is responsible for generating customer loyalty events, when a customer enters the
rewardsemail. This data is not persisted or tracked anywhere.quarkuscoffeeshop-inventory - The inventory service is responsible for tracking food and drink inventory.
quarkuscoffeeshop-customermocker - The customermocker can be used to generate test traffic.
quarkuscoffeeshop-majestic-monolith - The
majestic monolithbuilds 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.
Similar to the store chart, the Database chart can be deployed in the same variety of 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.
