Fwd: RabbitMQ as Abstraction layer

7 views
Skip to first unread message

Gregory Kelleher

unread,
Nov 1, 2011, 12:54:24 PM11/1/11
to raxa-jss-e...@googlegroups.com


-- Greg


Begin forwarded message:

From: Gregory Kelleher <gr...@kelleher.cc>
Date: October 15, 2011 11:21:27 AM EDT
To: Saptarshi Purkayastha <sun...@gmail.com>
Cc: Manor Lev-tov <manor...@gmail.com>, Daniel Pepper <daniel...@gmail.com>, Surajit Nundy <nun...@gmail.com>, judy wawira <judyw...@gmail.com>
Subject: RabbitMQ as Abstraction layer

Saptarshi,

Though you and I briefly du udder the de-coupling proposal, it was largely overlooked in the discussion on Friday.  Rephrased, the prop could be stated:

Systems interconnect by reading from and writing to an enterprise message queuing system, specifically RabbitMQ.

I know you had some concerns when it was first proposed.  Do you still have questions or concerns?  What's the status of this proposal?

Reasons I ask is that if we choose to decouple, the queuing system provides the abstraction layer for communication among HTML5 forms, OpenMRS, and CouchDB.  OpenMRS has no current interface for RabbitMQ --though it's badly needed-- and providing that interacts may be a good Stanford sprint project.

-- Greg

Do no harm, waste no fortune.

Reply all
Reply to author
Forward
0 new messages