Message Oriented Middleware

Message-oriented middleware or Message Oriented Middleware ( MOM) called middleware, which is based on the asynchronous or synchronous communication, ie, the transmission of messages ( Messages). The format for the message is not defined, but in practice XML has established itself as a popular format.

MOM supports three different communication protocols

  • Message Passing ( Direct communication between applications)
  • Message Queueing ( Indirect communication through a queue )
  • Publish & Subscribe (Editor provides subscriber messages available )

Benefits

  • Asynchronous / synchronous communication
  • Server / service must be available immediately
  • Message queues
  • Usually faster execution as a function call -based programs
  • Loose coupling of servers / clients
  • More tolerance for changes to the existing functions
  • Improved availability of the systems
  • Parallel processing of messages possible

Disadvantages

  • Failure of MOM paralyzes all connected systems
  • Designing, testing, debugging and development of the components are unfamiliar to synchronous programmer

Standards and Formats

MOM products

The following products are an arbitrary selection of MOM products on the market:

  • Websphere MQ IBM (formerly MQSeries )
  • XmlBlaster of xmlBlaster.org
  • Apache ActiveMQ as the JMS broker is also available with Apache Camel (both from the Apache Software Foundation )
  • RabbitMQ as AMQP broker
  • Fiorano ESB and Fiorano MQ of Fiorano Software
  • SAP Process Integration SAP
  • All Java EE application server ( through JMS support)
  • Microsoft Message Queue / Microsoft Message Queue Server
Asynchronous I/O Debugger XML template engine Markup language Enterprise Service Bus Web Services Description Language Query language Data conversion Java Message Service Advanced Message Queuing Protocol Technical standard Java Community Process IBM WebSphere MQ Microsoft Message Queuing Java Business Integration
565721
de