Architectural overview
Learn about the components of the Messaging Service and how they are organized.
The server to client push architecture is used to keep UI content updated with event-based information beyond the last server interaction. The messaging service uses WebSocket technology to maintain the connections between the browser and server.
The communication between the Messaging Service and browser must follow the standard messaging format. For more information on the messaging format and schema, see .
Architecture
Browser components subscribe to topics on the Message Broker through a WebSocket connection. Data sources such as Infinity publish data to the Message Broker through a HTTP REST connection. The Message Broker pushes this new information to those browsers that have registered an interest in this information.
Security
In the Messaging Service, the JSON Web Tokens (JWT) and the data to be published are validated to ensure secure WebSocket connections and trustworthy browser calls.
When the WebSocket connection is being created for the browser, the JWT issued by Infinity to the user during their login is validated with the JWKset file issued by Infinity directly to the Constellation Message Broker. The WebSocket connection is created only if this validation is successful.
Previous topic Working with Messaging Service Next topic Message schema