This is an example demo showing a retail store consisting of several microservices based on Red Hat OpenShift Application Runtimes (Spring Boot, WildFly Swarm, Vert.x, JBoss EAP and Node.js) deployed to OpenShift.
It demonstrates how to wire up small microservices into a larger application using microservice architectural principals.
1.1.x
There are several individual microservices and infrastructure components that make up this app:
- Catalog Service - Java application running on JBoss Web Server (Tomcat) and MongoDB, serves products and prices for retail products
- Cart Service - Spring Boot application running on JDK which manages shopping cart for each customer
- Inventory Service - Java EE application running on JBoss EAP 7 and PostgreSQL, serves inventory and availability data for retail products
- Pricing Service - Business rules application for product pricing on JBoss BRMS
- Review Service - WildFly Swarm service running on JDK for writing and displaying reviews for products
- Rating Service - Vert.x service running on JDK for rating products
- Coolstore Gateway - Spring Boot + Camel application running on JDK serving as an API gateway to the backend services
- Web UI - A frontend based on AngularJS and PatternFly running in a Node.js container.
In order to deploy the CoolStore microservices application, you need an OpenShift environment with
- 4+ GB memory quota if deploying CoolStore
- 16+ GB memory quota if deploying the complete demo
- RHEL and JBoss imagestreams installed (check Troubleshooting section for details)
- Nexus Repository (or other maven repository managers) with proxy repositories defined for JBoss Enterprise Maven Repository
Deploy the CoolStore microservices application using this template openshift/coolstore-template.yaml:
oc login -u developer
oc new-project coolstore
oc process -f openshift/coolstore-template.yaml | oc create -f -
When all pods are deployed, verify all services are functioning:
oc rsh $(oc get pods -o name -l app=coolstore-gw)
curl http://catalog:8080/api/products
curl http://inventory:8080/api/availability/329299
curl http://cart:8080/api/cart/FOO
curl http://rating:8080/api/rating/329299
curl http://review:8080/api/review/329299
In order to deploy the complete demo infrastructure for demonstrating Microservices, CI/CD, agile integrations and more, either order the demo via RHPDS or use the following script to provision the demo on any OpenShift environment:
$ oc login MASTER-URL
$ openshift/scripts/provision-demo.sh deploy msa-cicd-eap
You can delete the demo projects and containers with:
$ openshift/scripts/provision-demo.sh delete msa-cicd-eap
Read the script docs for further details and how to run the demo on a local cluster with oc cluster.
-
If you see an error like
An error occurred while starting the build.imageStream ...it might be due to RHEL or JBoss imagestreams not being installed on your OpenShift environment. Contact the OpenShift admin to install these imagestreams with the following commands:oc login -u system:admin oc delete -n openshift -f 'https://raw.githubusercontent.com/jboss-openshift/application-templates/master/jboss-image-streams.json' oc delete -n openshift -f 'https://raw.githubusercontent.com/openshift/openshift-ansible/master/roles/openshift_examples/files/examples/v1.3/image-streams/image-streams-rhel7.json' oc delete -n openshift -f 'https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis-image-streams.json' oc create -n openshift -f 'https://raw.githubusercontent.com/jboss-openshift/application-templates/master/jboss-image-streams.json' oc create -n openshift -f 'https://raw.githubusercontent.com/openshift/openshift-ansible/master/roles/openshift_examples/files/examples/v1.3/image-streams/image-streams-rhel7.json' oc create -n openshift -f 'https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis-image-streams.json' -
If you attempt to deploy any of the services, and nothing happens, it may just be taking a while to download the Docker builder images. Visit the OpenShift web console and navigate to Browse->Events and look for errors, and re-run the 'oc delete ; oc create' commands to re-install the images (as outlined at the beginning.)