Server Roles and Jobs

EmpowerID microservices are inherently purpose-built and perform their own intrinsic role. The EmpowerID UI and Worker containers are more general and can be configured as to exactly which jobs and API endpoints they should host in any installation. This is especially important for on-premise installations of EmpowerID but still very useful to understand for SaaS. The following discussion pertains only to the UI and Worker role containers. In the on-premise deployment model, the UI container role is known as Front-End servers, and the Worker container role is known as Back-End servers.

Key points

Each UI or Worker container in the EmpowerID Landscape is assigned a “Role” in the EmpowerID ecosystem. These roles are determined based on the assigned jobs and web services (REST API endpoints) the server will support.
UI containers primarily host the Web Services that support workflow processes and the UI web user interface.
Worker containers primarily host the Server jobs that support long-running security, data synchronization, and automated policy-based processes.
All jobs and web services can run on more than one container at a time for load-balancing and fail-over

Access Self-Service

Server Roles and Jobs

Key points

Each UI or Worker container can only be assigned one server role

Each Role is Assigned Jobs

Each Role is Assigned Web Services

You May Create New Server Roles

Demo