Note this project traces it's ancestry to this project created by Matt Stine Fortune-Teller This project focuses on Pivotal Cloud Foundry Deployment, and certain changes to demonstrate capabilities there.
Application Description
Fortune Teller is a very basic application composed of two services:
- Fortune Service - serves up random Chinese fortune cookie fortunes
- Fortune UI - presents a UI that consumes the fortune service
It leverages libraries and services from Spring Cloud and Netflix OSS to compose the system.
This application can be deployed locally leveraging the local instances of the Spring Cloud Services as Spring Boot apps (eureka, hystrix dashboard, config server)
Fortune Teller is also deployable to any Cloud Foundry environment that have installed the Spring Cloud Services package.
Building
Using the included Maven wrapper in each of the projects (note the root parent pom file is included as a local relative path)
Mac/Linux
$ ./mvnw package
Windows
$ ./mvnw.cmd package
The Maven wrapper will automatically download all the required Maven Libraries and all of Fortune Teller's dependencies. This may take a few moments.
Create the required services required for application deployment.
| Service Type | Service Name | Service Plan | Name |
|---|---|---|---|
| Config Server | p-config-server | standard | config (**see create time configuration) |
| Service Registry | p-service-registry | standard | svcreg |
| Circuit Breaker Dashboard | p-circuit-breaker-dashboard | standard | cbdash |
| Database | p-mysql | 100mb | fortunedb |
from command line you can configure the service at create time with -c and the following json
'{"count":1,"git":{"uri":"https://github.com/aripka-pivotal/config-repo.git"}}'
Wait for created services to reach a last operation of "create succeeded"
Push the microservices:
The Fortune Service and Fortune UI contain manifests so they may be pushed with the following simple commands. Update the manifest.yml file in each to reflect desired changes.
$ cf push
Testing the Application
In a browser, access the fortunes-ui application at the route that was created for you:
From Pivotal Cloud Foundry Apps Manager, access the Hystrix Dashboard by clicking on the Manage link for the cbdash service.
Access the fortunes-ui and show that the circuit breaker is registering successful requests.
Stop the fortunes application:
$ cf stop fortune-service
Access the fortunes-ui and see that the fallback fortune defined in the configuration git repo is being returned. (see the ui.yml file)
Access the fortunes-ui and show that the circuit breaker is registering short-circuited requests.
(Note due to the circuit breaker threshold settings are set at an extremely low threshold of 3. If you want to change this setting to the default value of 20 remove the hystrix.command.randomFortune.circuitBreaker.requestVolumeThreshold property from the Fortune-UI application.yml file. Removing this property will require a higher induced load which can be accomplished on Mac/Linux systems using the load.sh script found in the root project. )
Start the fortune-service application:
$ cf start fortune-service
Continue to access the fortunes-ui and watch the dashboard.
After the fortunes service has re-registered with Eureka and the fortunes-ui load balancer caches are refreshed, you will see the circuit breaker recover. This may take up to 30 seconds
You should then start getting random fortunes again!
Provided Scripts
The root project contains provided scripts (see scripts directory that can be used on Mac/Linux systems to create load on the UI app, and stop the fortune-service unexpectedly that will cause Pivotal Cloud Foundry to restart it.
There is also a refresh script that will trigger a reload of the properties from the config server after a change to the properties in the git repo. (Note you will need to clone the provided git repo, or provide your with a ui.yml file.)