Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Architectural overview

Updated on July 20, 2021

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 .


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.

Messaging Service Architecture
Architecture diagram of the Constellation Messaging Service depicting it serving as a bridge between subscribers and data sources.


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.

Messaging Service Authentication
A workflow depicting the various authentication steps performed by the Messaging Service.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us