4. Speaker
• Specialist II
• Working in Hashedin By Deloitte
• 3+ Years of Experience
• 3x MuleSoft Certified
• 3x AWS Certified
• 2x GCP Certified
ROBIN SINHA
7. The Power of Real-Time: Synchronous
Integration Pattern
● The synchronous approach is used to process messages in the same thread that initially
received the message.
● After the flow receives a message, all processing, including the processing of the response,
is done in that same thread.
● The flow needs to meet the requirements of transactional processing.
● This means that a transactional flow must not hand off processing to other threads, where
errors can occur after the transaction is completed.
● The flow’s inbound endpoint must be notified of all errors that occur during the processing of
the message.
9. Embracing Delays : Asynchronous Integration
Patterns
● The Asynchronous approach processes the message simultaneously with the parent
message flow.
● This means that you have an activity in the flow that can be processed without
stopping the flow.
● There are some time-consuming operations (printing a file or sending SMTP email)
which don’t have a dependency in further flows.
● To avoid the waiting, we use asynchronous processing.
● Fire and Forget
11. Ways to achieve async processing,
● Async Scope
● Scheduler
● Event Processing
Message broker
■ Eg: JMS, VM
Component supporting trigger based on events
■ Eg: On Table Row, On New or Updated File
13. Java Messaging Service
Used to create, send, receive and read
messages or exchange messages between
different systems.
Some Enterprise applications may have ‘n’
number systems and they exist in different
locations. They use different platforms. If
they want to exchange information in a
loosely coupled manner, then we should
use JMS Messaging system.
14. Point-to-Point
● One message is delivered to one receiver only. Here, Queue is used
as a message-oriented middleware (MOM).
● The Queue is responsible to hold the message until receiver is ready.
● There is no timing dependency between sender and receiver.
15. Pub/Sub
● One message is delivered to all the subscribers. It is like
broadcasting. Here, Topic is used as a message-oriented middleware
that is responsible to hold and deliver messages.
● There is timing dependency between publisher and subscriber.
