Recommended
Recommended
More Related Content
Similar to Mastering the Puzzle Integration Patterns Decoded | MuleSoft Mysore Meetup #35
Similar to Mastering the Puzzle Integration Patterns Decoded | MuleSoft Mysore Meetup #35 (20)
More from MysoreMuleSoftMeetup
More from MysoreMuleSoftMeetup (20)
Recently uploaded
Recently uploaded (20)
Mastering the Puzzle Integration Patterns Decoded | MuleSoft Mysore Meetup #35
- 1. Mysore MuleSoft Meetup 29-Sep-2023 Mastering the Puzzle: Integration Patterns Decoded 💡
- 2. AGENDA • Introduction • Integration Patterns The Architect's Toolbox: Overview of Integration Patterns Sync or Swim? Navigating Integration Patterns The Power of Real-Time: Synchronous Integration Patterns Embracing Delays: Asynchronous Integration Patterns Real-World Use Cases • Q&A • Networking time • Wrap-Up
- 3. Organizers Shubham Chaurasia Billennium India Pro Integration Developer Giridhar Meka Sr. Technical Architect linkedin.com/in/giridharmeka linkedin.com/in/shubhamchaurasia1 Priya Shaw LTI MindTree Sr. Integration Specialist linkedin.com/in/priya-shaw
- 4. Speaker • Specialist II • Working in Hashedin By Deloitte • 3+ Years of Experience • 3x MuleSoft Certified • 3x AWS Certified • 2x GCP Certified ROBIN SINHA
- 5. Mastering the Puzzle: Integration Patterns Decoded
- 6. Sync or Swim? Navigating Integration Patterns ● Synchronous ● Asynchronous Types
- 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.
- 8. Synchronous
- 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
- 10. Asynchronous
- 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
- 12. Event Processing Messaging Models Point-to-Point Publisher/Subscriber
- 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.
- 16. Some Common Integration Architectures Point-to-Point Integration Hub-and-Spoke Integration Publish-Subscribe Integration Message Broker Integration API Gateway Integration Batch Integration File-Based Integration Microservices Integration EAI (Enterprise Application Integration) Service-Oriented Architecture (SOA)
- 19. Networking time
- 20. Thank You