The primary responsibility of a message endpoint is to connect your application code to the underlying messaging infrastructure. It should do this in such a way that the application code is not tied to a messaging structure and that it doesn’t have any knowledge of either the message or the message channels.
Message endpoint in many ways is compared to as a controller in MVC architecture. In MVC controller handles the HTTP request and is mapped to URL’s in the similar way as endpoints handles messages and is mapped to the message channels. The point to be noted here is that both controller and endpoints does this by isolating the application code from the underlying infrastructure details which is important in avoiding the level of complexity arising out of it.
There are varieties of message endpoints, which can be summarized as shown below:
- Channel Adapter
- Service Activator
Channel adapter, Gateway and Service Activator endpoints allows connections to your application or to the outside world. However other endpoints listed above does more of message translations, splitting, routing etc. We will now see these message endpoints in some detail in the following sections.
Page Visitors: 11712