Message Oriented Middleware

Message Oriented Middleware

1. Message Oriented Middleware
-An Overview
Behzad Altaf

2. Messaging

3. Middleware
Middlewareis computersoftwarethat provides services tosoftware applicationsbeyond
those available from theoperating system. It can be described as "software glue".
https://en.wikipedia.org/wiki/Middleware

4. Types of Middleware
https://en.wikipedia.org/wiki/Middleware_(distributed_applications)
Message-oriented middleware
Enterprise messaging system
Enterprise service bus
Intelligent middleware
Content-centric middleware
Remote procedure call
Object request broker
SQL-oriented data access
Embedded middleware
Other
Transaction processing monitors
Application servers

5. Message Oriented Middleware
Message Oriented Middleware is a specific class of middleware that supports the
exchange of general-purpose messages in a distributed application environment.
http://courses.ischool.berkeley.edu/i206/f97/GroupB/mom/what_is_mom.html

6. MOM –why?
Decoupled
Integrated platforms /languages
Reliable Communication
Disconnected
Throttled
Scalability

7. MOM –Decoupled

8. MOM –Integrated platforms / Languages
Java Ruby
C SOAP/REST
Message
Broker

9. Messaging -Communication
Introduction to Enterprise Service Bus ftp://ftp.oreilly.com/pub/summit/ch05.pdf

10. MOM –Reliable Communication
Introduction to Enterprise Service Bus ftp://ftp.oreilly.com/pub/summit/ch05.pdf

11. At most ONCE
Messages may be lost but
are never redelivered.
At least ONCE
Messages are never lost but
may be redelivered.
Exactly ONCE
Each message is delivered
once and only once.
Message Delivery Semantics
MOM –Reliable Communication
http://kafka.apache.org/documentation.html#semantics

12. MOM –Disconnected

13. MOM –Throttled

14. MOM –Scalability

15. MOM -need

16. ??????
??????−1
2
MOM -need

17. Introduction to Enterprise Service Bus ftp://ftp.oreilly.com/pub/summit/ch05.pdf
MOM -need

18. MOM -need

19. Introduction to Enterprise Service Bus ftp://ftp.oreilly.com/pub/summit/ch05.pdf
MOM -need

20. MOM -concepts
Introduction to Enterprise Service Bus ftp://ftp.oreilly.com/pub/summit/ch05.pdf

21. MOM -concepts
Introduction to Enterprise Service Bus ftp://ftp.oreilly.com/pub/summit/ch05.pdf

22. MOM -concepts

23. Middleware -Providers

24. Case for JMS
The Java Message Service (JMS) API is a Java Message Oriented Middleware (MOM)
API for sending messages between two or more clients.

25. Case for AMQP
The Advanced Message Queuing Protocol (AMQP) is an open standard application layer
protocol for message-oriented middleware. The defining features of AMQP are message
orientation, queuing, routing (including point-to-point and publish-and-subscribe),
reliability and security.

26. Case for OpenMAMA
OpenMAMA is a high performance Middleware Agnostic Messaging API that provides a
consistent abstraction layer over a variety of message oriented middle wares.
Each middleware interfaces with OpenMAMA using an adapter known as a 'bridge', the
bridge then translates OpenMAMA function calls into the native functions of the
selected middleware/s allowing developers to code to a single, clean, simple and open
API.

27. MOM –the pitfalls
Extra Layer to worry about.
Mostly proprietary solutions.
Integration is not an easy exercise.
Time
Expertise
Async has it’s own issues.

28. MOM –Further reading
•Enterprise Integration Patterns
–G. Hohpe, B Woolf
http://www.enterpriseintegrationpatterns.com/