Enterprise Service Bus – Concept and Use-case


Published on

Enterprise Service Bus - Concept and Use case

How APPSeCONNECT uses ESB to integrate SAP Business One and Magento

Published in: Technology

Enterprise Service Bus – Concept and Use-case

  1. 1. Enterprise Service Bus Concept and Use case How APPSeCONNECT uses ESB to integrate SAP Business One and Magento
  2. 2. Agenda • Problems with Point-Point connectivity • What is Enterprise Service Bus and why it is important? • Some implementations of ESB • How APPSeCONNECT uses ESB for integration • A use case for our SAP B1 – Magento integration using ESB.
  3. 3. Problems with Point to point integration without ESB
  4. 4. Lets say in hypothetical scenario, You have a business and you control your business using App 1
  5. 5. Your business expands and you need some more applications specific to solve your particular problems of your business. But what about the communication between them ? One, you might write all logic inside App 1 and communicate data to and from App 2 and App 3.
  6. 6. Few more applications add as time goes on, and you need to continually upgrade your main App1 to support additional apps.
  7. 7. But all of a sudden, you require the connected apps need to send some data between them. You can do by proxy the data from App 1 but it will make App 1 very complex and hard to maintain.
  8. 8. Enterprise Service Bus Why it is important ?
  9. 9. Why ESB is important • Enterprise service Bus is a service layer which lies between the interactive applications so that they can talk to each other using standard protocol. • Maintenance of application in forms of adding more and more applications and removing applications is easy. • One single point failure but yet can be load balanced.
  10. 10. Duties of ESB • Self-monitored control of messages exchanged between communicating parties. • Distributing information across intended parties quickly and easily. • Use of common protocols. • Retain messages when intended parties are offline or not available for message consumption. • Changing, re-routing, logging information can be made anytime without changing the implementation of Service Bus. • Providing incremental solutions to the problem.
  11. 11. Benefits of ESB • Totally decoupled architecture. • Can support heterogeneous architecture without any change. • Less infrastructure code required to add more apps. • Generalized solution to the problem • Easier to scale up. • Message based approach rather than contract based approach. • Messages are sent using common standard protocol.
  12. 12. Supports: • Message-based contract • Message Routing • Security
  13. 13. Some implementations of ESB Concepts
  14. 14. ESB Implementations Message Queues Grouped Relays
  15. 15. Service Bus Queues
  16. 16. Service Bus Groups
  17. 17. Service Bus Relays
  18. 18. Service Bus Relays
  19. 19. Service Bus Relays
  20. 20. Service Bus Relays
  21. 21. Service Bus Relays
  22. 22. Service Bus Relays
  23. 23. Service Bus Relays
  24. 24. Service Bus Relays
  25. 25. ESB usages in APPSeCONNECT
  26. 26. Kind of Communication in APPSeCONNECT • Message based Communication • Real-Time communication • Relay based communication • Event messages for sync activities.
  27. 27. Magento – SAP Business One (A use case)
  28. 28. Communication Channels • SOAP message based communication channel. • Socket based communication channel. • Configures a self hosted Enterprise Service Bus on premise for realtime touchpoints.
  29. 29. Questions We are happy to answer your questions! For more details about APPSeCONNECT, visit www.appseconnect.com /appseconnect /company/insync
  30. 30. Thank you For more such webinars, visit: www.appseconnect.com/webinars