Runtime View
Table of Contents
1. Overview
Figure 1. Overview of the usage of the kp-users by other SCS and their users.
| 1 | At system startup the SCS subscribe to the user management topics on the message broker. |
| 2 | The user accesses the other-scs with a HTTP request. |
| 3 | The process gets handled by the ingress controller which forwards the request to the service. |
| 4 | The service load "balances" the request to one of the pods (there is only one). |
| 5 | The handling is done in parallel of serving the request. 5a: The pod sends the login event to the broker. 5b: The broker load balances the request to one of the broker pods. 5c: the event is sent to all subscribers of the topic. |
| 6 | The pod send the content with a transclude to kp-users to the user (via ingress). |
| 7 | The user gets the content with the transclude. |
| 8 | The user requests the transclude from the kp-users SCS. |
| 9 | The request is handled by the ingress controller which forwards the request to the service. |
| 10 | The service load balances the request to one of the pods. |
| 11 | The pod serves the transcluded content. |
| 12 | The ingress controller returns the transcluded content to the user. |