Kubernetes deployments for the t2 store, the databases and the cdc.
| directory / file | content |
|---|---|
| ./cdc/ | deployment for cdc service and its database |
| ./notsaga/ | kube files for the T2 services that are not part of the saga |
| ./saga/ | kube files for the T2 services that participate in the saga |
| ./testsetup/ | kube files for the e2e test service and kube files for ui backend and payment in test mode |
| ./loadprofiles/ | load profiles for the Apache jMeter load generator |
| ./prometheusfiles/ | config / rules / alerts for prometheus |
| ./setenv.sh | export environment variables required do build the T2 store locally |
The eventuate tram CDC service and its database. It requires the message broker to be up.
The database uses the image provided by eventuateio, because that database all ready has the required tables and schemas.
The kube file for the CDC service is derived from this docker-compose file: https://github.com/eventuate-tram/eventuate-tram-sagas-examples-customers-and-orders/blob/master/docker-compose-postgres.yml
The T2 Stores saga participants. They require the message broker, the databases and the CDC service to work properly. The Payment Service also requires a the payment provider.
- orchestrator-cs : cluster service such that other services can talk to the Orchestrator.
- inventory-cs : cluster service such that other services can talk to the Inventory.
The T2 Store services that are not part of the saga.
The Cart Service requires the mondoDB database and the UI Backend requires the Orchestrator, Inventory and Cart Service to work properly.
- provider-cs : cluster service to talk to the payment provider.
- uibackend-cs : cluster service to talk to the ui backend.
- ui-cs : cluster service to talk to the ui.
exists such that you can talk to the UI Backend from outside of the cluster.