generate manifest files with correct version number in far filename as part of build.

improve controllers so we can have better API management (i.e. versioning). For example, have "/v1/" in the path so we can have multiple concurrent versions.

Also, try to improve APIs (format, syntax, structure, docs).

at specific times of day, the UI displays nothing and curling the UI gives the following error:
{"timestamp":1452867880919,"status":500,"error":"Internal Server Error","exception":"org.thymeleaf.exceptions.TemplateProcessingException","message":"Error formatting decimal with minimum integer digits = 0, thousands point type = COMMA, decimal digits = 2 and decimal point type = POINT (fragments/marketsummary_fragment:67)","path":"/"}

Seems to suggest there is something wrong with the data passed to the UI.

Extend quote service to provide a REST endpoint to retrieve multiple quotes in one request.

This will improve performance of web and portfolio services

2018-03-08 02:53:46.904 ERROR 8608 --- [trace=,span=] [ main] o.s.boot.SpringApplication : Application startup failedjava.lang.IllegalStateException: Could not evaluate condition on org.springframework.cloud.netflix.ribbon.eureka.RibbonEurekaAutoConfiguration due to org/springframework/cloud/context/named/NamedContextFactory not found. Make sure your own configuration does not rely on that class. This can also happen if you are @ComponentScanning a springframework package (e.g. if you puΓÇ¿ at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:55) ~[spring-boot-autoconfigure-1.4.5.RELEASE.jar:1.4.5.RELΓÇ¿ at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:43ΓÇ¿ at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.javΓÇ¿ at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:116) ~[spring-conteΓÇ¿ at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:320) ~[spring-context-4.ΓÇ¿ at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:228) ~[spring-conteΓÇ¿ at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitio nΓÇ¿ at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:93) ~[spring-contextΓÇ¿ at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:686) ~[spring-context-4.3.7.RELEASΓÇ¿ at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122) ~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELΓÇ¿ at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) ~[na:1.8.0_162]:1.8.0_162]Factory.RELEASE.jar:1.4.5.RELEASE]5.RELEASE] tΓÇ¿ at org.springframework.core.type.classreading.AnnotationReadingVisitorUtils.convertClassValues(AnnotationReadingVisitorUtils.java:78) ~[spring-core-4.3.7.RELEASE.jaΓÇ¿ at org.springframework.core.type.classreading.AnnotationMetadataReadingVisitor.getAnnotationAttributes(AnnotationMetadataReadingVisitor.java:134) ~[spring-core-4.3.ΓÇ¿ at org.springframework.core.type.classreading.AnnotationMetadataReadingVisitor.getAnnotationAttributes(AnnotationMetadataReadingVisitor.java:127) ~[spring-core-4.3.ΓÇ¿ at org.springframework.core.type.classreading.AnnotationMetadataReadingVisitor.getAnnotationAttributes(AnnotationMetadataReadingVisitor.java:49) ~[spring-core-4.3.7ΓÇ¿ at org.springframework.boot.autoconfigure.condition.OnBeanCondition$BeanSearchSpec.(OnBeanCondition.java:290) ~[spring-boot-autoconfigure-1.4.5.RELEASE.jar:1.ΓÇ¿ at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchOutcome(OnBeanCondition.java:79) ~[spring-boot-autoconfigure-1.4.5.RELEASE.jar:1.4.5.RELΓÇ¿ at org.springframework.boot.autoconfigure.condition.AbstractNestedCondition$MemberOutcomes.getConditionOutcome(AbstractNestedCondition.java:194) ~[spring-boot-autocΓÇ¿ at org.springframework.boot.autoconfigure.condition.AbstractNestedCondition$M eΓÇ¿ at org.springframework.boot.autoconfigure.condition.AbstractNestedCondition$MemberConditions.getMatchOutcomes(AbstractNestedCondition.java:165) ~[spring-boot-autocoΓÇ¿ at org.springframework.boot.autoconfigure.condition.AbstractNestedCondition$MemberMatchOutcomes.(AbstractNestedCondition.java:80) ~[spring-boot-autoconfigure-ΓÇ¿ at org.springframework.boot.autoconfigure.condition.AbstractNestedCondition.getMatchOutcome(AbstractNestedCondition.java:64) ~[spring-boot-autoconfigure-1.4.5.RELEAΓÇ¿ at org.springframework.boot.autoconfigure.condition.AllNestedConditions.getMatchOutcome(AllNestedConditions.java:45) ~[spring-boot-autoconfigure-1.4.5.RELEASE.jar:1ΓÇ¿ at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:47) ~[spring-boot-autoconfigure-1.4.5.RELEASE.jar:1.4.5.RELΓÇ¿ ... 42 common frames omitteddClass(ClassLoader.java:357) ~[na:1.8.0_162]8.0_162]NamedContextFactory
2018-03-08 02:53:46.904 INFO 8608 --- [trace=,span=] [ main] ationConfigEmbeddedWebApplicationContext : Closing org.springframework.boot.contex

something similar to https://github.com/vinayu/CloudNativeArchitectureClass/blob/tiaa/day_01/session_01/lab_04/lab_04.adoc#build-and-version-control-info

As a working demo of microservices in action, Spring Trader lends itself very well to showing continuous delivery and zero-downtime deployments. Individual services can easily be tested and updated while the application as a whole continues to operate.

Jenkins is the most popular field tool for CI/CD demos, but the project as currently organized doesn't work well with Jenkins. Jenkins can generate generic "something in this Github repo has changed" events, and trigger a build off of that. But the Github plugin for Jenkins will not work at the granularity of identifying which files have changed, in order to determine which services need to be deployed.

So for field demos, we have had to clone the project, and set up a "one-repo-per-microservice" structure in order to create a Jenkins demo that can build and deploy the correct service on code change.

Does it make sense to reorganize this project in that way, or is there a suggested alternative method for doing CI/CD demos?

create a Mobile UI to show off the mobile services of PCF

Add session state caching to the web service so we can scale it.

Upgrade web UI to a more version of bootstrap. Currently using bootstrap 2.3.2.

The quote service is using markitondemand to retrieve quote and company information. This is being used because it is free with no limits on number of calls. However, it is very temperamental.

A secondary service should be added, yahoo finance for example, with hystrix to handle the failed calls to markitondemand.

Currently the summary of quotes on page header is 3 FS and 3 IT quotes picked at random from a list. And the market summary is hard coded to zeros.

There should be a service to retrieve this information from somewhere and instead of being 3 FS and 3 IT quotes, should be 3 top performers and 3 worst performers.

Add correlations IDs to all the calls between the micro services so we can trace user interaction across micro services.

Then we will be able to use the ELK tile to display nice dashboards with relevant information

Currently we have ok unit test coverage for quotes, accounts and portfolio (although probably should have more and better ones).

Issues are:

• some unit tests are not really unit tests as they call out to external services. these should be contained to code.
• no integration testing

Building a CI pipeline using concourse, so probably a good idea to have more automated testing as this will allow to release more often.

It would be good if we could have integration testing for each service and also some end-2-end testing (maybe with selenium???)

Add turbine and aggregate all hystrix metrics into the dashboard.

Create the demos and documentation for the demos listed in the docs.

The build fails due to not being able to parse dates from json:

`
java.text.ParseException: Unparseable date: "Wed May 6 00:00:00 UTC-04:00 2015"

at java.text.DateFormat.parse(DateFormat.java:366)

at io.pivotal.quotes.configuration.TestConfiguration.quote(TestConfiguration.java:43)

`

and
`
com.fasterxml.jackson.databind.JsonMappingException: Failed to parse Date value 'Thu Jun 11 00:00:00 UTC-04:00 2015' (format: "EEE MMM dd HH:mm:ss zzzXXX yyyy"): Unparseable date: "Thu Jun 11 00:00:00 UTC-04:00 2015" (through reference chain: io.pivotal.quotes.domain.Quote["Timestamp"])

        at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:210)

        at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:177)

`

Thanks to @flambiente-pivotal for uncovering this.

Portfolio is taking too long retrieving quotes which makes web timeout.

Fix and enhance the logging within the micro services to a more logical, standard way.

Add config server to the architecture so all services get their config from the config server.

Add oauth

Services are crashing due to running out of meatspace.
2015-10-18T10:28:45.12+0100 [App/0] OUT # 2015-10-18T10:28:45.12+0100 [App/0] OUT # java.lang.OutOfMemoryError: Metaspace

Split account service into a user account and a DDA - Demand Debit Account Service. The user account is responsible for the user information (id, name, address, password, etc). The DDA is responsible for keeping track of the transactions on the account (i.e. debits and credits) and overall balance.

Also, the password should be split out from the "account" object and stored safely, i.e. a salted.

Portfolio service should use Hystrix when calling the quote service. Currently, when fetching a quote fails, retrieving the portfolio fails completely. It should at least send back the list of transactions.

Adding documentation for running the services locally, as well as in a cloud without Spring Cloud Services for Pivotal Cloud Foundry

When an order fails (either not enough funds or cannot access the accounts service), the web service displays the error page without any information.

Quotes service failure rate is higher when US is awake.

Some micro services cannot run locally, any that depend on user-provided services. The services use spring cloud connectors to know about each other and only the cloud foundry connectors have been implemented.

Cannot change balance after so creating account with 0 balance is useless

The dropdown menu with the logout link in the navbar of the UI is not working and thus logout can't be reached.

Update to use the GA version of Spring Cloud Services

account and token for use of XIgnote service has expired.

We shouldn't really be using services that we need to register for, or that there are expiration dates or low threshold limits of use.

Need to add to the docs on how to create account and change token for now, but look at using different service - specially now that we have yahoo quotes as well.

There should be a fallback method in case portfolio isn't available.

Add a caching service to the quotes service so that we don't have to go to the external service every time. Use expiry to remove stale data from the cache.

Currently, services don't bind to Eureka deployed with Spring Cloud Services for CF. It should be possible to make them bind to Eureka, whether it is deployed, locally, manually in CF or through the Spring Cloud Services.