Skip to main content

Internal HTTP Communication for Applications

This feature introduces a sophisticated method for applications to communicate internally using HTTP protocols and unique aliases. By leveraging HTTP, it eliminates the dependency on external endpoints, offering a secure and efficient pathway for applications to exchange messages. This approach enhances the interoperability among applications, facilitating a direct and simplified communication model within the system's architecture.

Creating Your Endpoint​

To enable HTTP-based communication between your application and others within the system, it is essential to set up an endpoint. This endpoint utilizes a unique alias assigned to your application, facilitating the secure and efficient routing of messages between applications. The endpoint's structure is defined as follows:

http://{alias}/{user-endpoint}
  1. {alias}: Represents the unique alias of your application, serving as a secure message routing mechanism.
  2. {user-endpoint}: Denotes the specific application endpoint intended for communication, designed to process HTTP requests from other applications.

Example​

For an application with the alias app123 aiming to receive messages at an endpoint named receiveMessage, the endpoint configuration would be:

http://app123/receiveMessage

This setup allows other applications to directly send HTTP messages to the receiveMessage endpoint of app123, facilitating efficient internal communication.