The DCM Dashboard architecture is an extension of the DCM 2.0 architecture that consists of several services working together.
The figure below shows the additional services, how they relate to the existing infrastructure and their communication and their storage.
Component / Function details:
Dashboard Frontend
The Blueriq Dashboard Frontend is the customer facing application which exposes dashboards.
The Dashboard Frontend has no persistent data.
The Dashboard Frontend communicates:
- All communication goes trough the Gateway Service
- With the DCM Dashboard Service via REST to retrieve dashboard definitions
- With the DCM 2.0 Infrastructure via REST to interact with the Runtime and DCM Lists Service
- With the IDP via REST to manage authentication and authorization
Gateway Service
The Blueriq Gateway Service is responsible for routing traffic from the Dashboard Frontend to other services. Additionally it can act as a Backend For Frontend to relay authentication tokens to downstream services.
The Gateway Service persists HTTP session data in Redis.
The Gateway Service communicates:
- Routes traffic to the DCM Dashboard Service
- Routes traffic to the DCM 2.0 Infrastructure
- Routes traffic to the IDP
DCM Dashboard Service
The Blueriq DCM Dashboard Service is responsible for serving definitions of dashboard applications.
The DCM Dashboard Service has no persistent data.
The DCM Dashboard Service communicates:
- With Gateway Service to serve dashboard definitions
DCM 2.0 Infrastructure
The DCM 2.0 Infrastructure is mentioned as a single node as the DCM Dashboard Services are an extension to the existing DCM 2.0 Architecture.
The DCM 2.0 Infrastructure persists HTTP session data in Redis.
The DCM 2.0 Infrastructure communicates:
- With Gateway Service to accept routed traffic