Communication between services
Requests made via the Web UI reach the Redaction Gateway via Ingress. The redaction gateway communicates with the different services, while the other services handle the communication with the persistence service.
The architecture includes a database for identity management (Keycloak) and a master database that handles tenant information and available tenants. Additionally, there are tenant-specific persistence systems, which consist of tenant databases (PostgreSQL and MongoDB) and dedicated tenant storage.
Internal communication within the system is asynchronous, using queues in RabbitMQ. Caching is handled by Redis.
Good to know:
The flow chart below is helpful for debugging.
The numbered dots show the process step(s) the services are involved in. (Please see the process steps diagram in the bottom right corner of the flow chart.)
Communication between the different RedactManager services