Page History

...

Integration tests run multiple services together to check that their interdependencies inter-dependencies work as intended.  Integration tests are named for the services they include.

...

demo-server is a project which uses the same methodology as the integration tests to deploy all the services together except the UI and to provision them .  Demo-server provisions the services in a generic way.  This is a reasonable place to start in playing with deployment.  You will need to understand its this provisioning code to be able to provision in your production environment.

It is unlikely that you will be able to build a production environment based solely on demo-server, because the microservices .  The services are designed for a cloud deployment in which services run in containers and scaling up is achieved by spinning up new instances.  Demo-server simply runs all the services on your own machine.runs one instance of each service, plus an embedded version of Eureka, Mariadb, Cassandra, and ActiveMQ locally.

Because Keep in mind that because of the number of processes involved and the resources required, startup of all the services is rather slow, and older in the demo-server can take up to 20 minutes.  Older computers may "choke" on the demo-server.  In particular, I strongly recommend all those processes.  I strongly recommend a computer with plenty of memory and with an SSD drive.

test-accounting-portfolio

Description:Tests the interaction between accounting and portfolio.  Because token validation requires a valid public key from identity, the test harness for this test is more sophisticated than for integration tests which contain provisioner and identity.

test-provisioner-identity-organization

Description:Mainly tests the interaction between provisioner and identity.  The "organization" in the name stands for "office", which is in there too, but it's secondary.

test-provisioner-identity-rhythm-portfolio-accounting

Description:Tests the interaction between the named services.  This test is currently portfolio-centric, since it is portfolio which requires all the other services.

service-starter

A library which starts services, eureka, and ActiveMQ for use in the integration tests and in demo-server.

...

Keeps track of accounts, ledgers, and journal entries.

office

Code name:  horus

Saves branches, and employees and their relationship to eachothereach other.  Employees should have a 1:1 relationship with users in the identity service.

...

Tracks customers, including their contact details and identification data.

group

Code name:  Description:ptah

Tracks groups of customers.  Intended for use in group loans, but has not yet been used from any other service or from the UI.  Incomplete.

deposit-account-management

Code name:  Description:shed

Tracks deposit products and deposit accounts for customers.

portfolio

Code name: bastetDescription:

Tracks loan products and loan accounts (aka cases) for customers.

teller

Code name:  Description:tajet

Provides management of teller cash.  Supports a customer-service-centric view of payment and repayment for deposit, and portfolio.

Libraries

Libraries are not deployable pieces of code.  They are intended to support the common functionality of the services.  Most library projects produce one build artifact and contain unit tests for its classes.

...