The Full Wiki



More info on Message Queuing as a Service

Message Queuing as a Service: Wikis


Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.

Encyclopedia

Updated live from Wikipedia, last check: June 04, 2012 03:11 UTC (37 seconds ago)

From Wikipedia, the free encyclopedia

Messaging as a Service is message oriented middleware or MOM deployed in a compute cloud using Software as a Service or SaaS model. When using MaaS, service subscribers access queues and or topics to exchange data using point-to-point or publish and subscribe patterns.

Contents

Goals

MaaS technology aims to eliminate the traditional overhead associated with operating in-house messaging infrastructures. These operating overheads include:

  • Unused capacity installed to meet peak demands
  • Human resources that are necessary to maintain messaging infrastructure
  • Projects idle time waiting for resource provisioning
  • Need to isolate messaging resources

Besides reducing cost, MaaS technology seeks to simplify access to messaging resources and therefore facilitate integration efforts within organizations and between them.

Benefits

MaaS technology also creates new value by providing reduced costs, enhanced performance and reliability. In order to provide those benefits, MaaS leverages cloud computing resources such as storage, network, memory and processing capacity. By using virtually unlimited cloud computing resources, MaaS technology provides internet scale messaging platform.

Accessibility

MaaS is accessible through a variety of protocols such as Java Message Service, AMQP, REST-Style APIs and Web Services.

Usage Examples

Patient gets admitted into a hospital out of her provider's network. Producer hospital can start sending real time events about the treatment of the patient to her physician's hospital using MaaS platforms. The cost of integration between hospitals is marginal since they do not need to configure messaging protocols, VPNs and other details.

Information processing organization that processes events from thousands of different sources, can ask its information providers to simply place messages onto MaaS queue and reduce integration costs.

Security trading application can post updates to P&L application that might be unavailable at the moment.

Technician submits an x-ray while consuming application instances in London, Chicago and Sao Palo compete who gets the message first by listening on the same queue.

Examples

  • Amazon Simple Queue Service - supports messages up to 8k; does not guarantee order or that message will be delivered once only. Supports REST API only. Utilizes Amazon Compute Cloud.
  • Gnip - specifically provides messaging resources for social networks and utilizes Amazon Compute Cloud.
  • cloudMQ - targets enterprise messaging users, supports large messages, XA transactions, guarantees message order and delivery and supports JMS. Uses Amazon EC2.
  • OpenMQ - proprietary open source platform.
  • OnlineMQ - web message queue. supports REST, SOAP and POX API, with PHP, Java & Ruby sample code.

References








Got something to say? Make a comment.
Your name
Your email address
Message
Please enter the solution to case below
12+8=