Enterprise Integration Patterns: Messaging Endpoints - 7.1

Talend ESB Mediation Developer Guide

author
Talend Documentation Team
EnrichVersion
7.1
EnrichProdName
Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for ESB
Talend Real-Time Big Data Platform
task
Design and Development > Designing Routes
EnrichPlatform
Talend ESB
Talend Runtime
Enterprise Integration Pattern Description

Messaging Mapper

(http://camel.apache.org/messaging-mapper.html)

Moves data between domain objects and the messaging infrastructure while keeping the two independent of each other.

Event Driven Consumer

(http://camel.apache.org/event-driven-consumer.html)

Enables an application to consume messages automatically as they become available.

Polling Consumer

(http://camel.apache.org/polling-consumer.html)

Enables an application to consume a message when the application is ready.

Competing Consumers

(http://camel.apache.org/competing-consumers.html)

Enables a messaging client to process multiple messages concurrently.

Message Dispatcher

(http://camel.apache.org/message-dispatcher.html)

Enables multiple consumers on a single channel to coordinate their message processing.

Selective Consumer

(http://camel.apache.org/selective-consumer.html)

Enables a message consumer to select which messages it wishes to receive.

Durable Subscriber

(http://camel.apache.org/durable-subscriber.html)

Enables a subscriber to avoid missing messages while it's not listening for them.

Idempotent Consumer

(http://camel.apache.org/idempotent-consumer.html)

Enables a message receiver to deal with duplicate messages.

Transactional Client

(http://camel.apache.org/transactional-client.html)

Enables a client to control its transactions with the messaging system.

Messaging Gateway

(http://camel.apache.org/messaging-gateway.html)

Encapsulates access to the messaging system from the rest of the application.

Service Activator

(http://camel.apache.org/service-activator.html)

Enables an application to design a service that can be invoked both via various messaging technologies and via non-messaging techniques.