On 01/08, Hugh Brock wrote:
Maybe a crazy idea, but Torquebox already includes messaging, background
jobs, services and all other things mentioned in the original email.
I have PoC of running Conductor inside Torquebox (using jRuby). I
understand it might be a big step but definitely worth to at least
investigate as an option :-)
Just my .20cents.
-- Michal
I have hated on message bus solutions publicly in the past, so it
seems
appropriate for me to weigh in now :).
What you're suggesting appears to make good sense. However, based on
past (bitter, painful, very expensive) experience, I would like us to
approach the message bus question very carefully, according to a few
principles:
* Any message bus, regardless how robust or stable, introduces
complexity and dependencies to our code. Any proposal to add message
bus use to one of our components should include some consideration of
the costs and benefits. In other words, I want to see a solid
justification of why REST callbacks are inadequate for a particular
API connection before we dive into AMQP.
* The message bus we choose should be one that other upstream cloud
projects commonly use. (What is OpenStack using, for example? Is oVirt
using anything?). It should also be available across our target
developer and end user platforms.
* The message bus we choose must support all the encryption and
authentication mechanisms that the app supports. This means LDAP,
oAuth, and (eventually) kerberos.
* Unless it is incredibly expensive to build it this way, I'd like the
message bus to be optional wherever possible -- meaning, fall back to
a simple listener/callback over REST architecture whenever possible.
Darts welcome :)...
--Hugh
--
== Hugh Brock, hbrock(a)redhat.com ==
== Engineering Manager, Cloud BU ==
== Aeolus Project: Manage virtual infrastructure across clouds. ==
==
http://aeolusproject.org ==
"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."
--Robert McCloskey
--
Michal Fojtik <mfojtik(a)redhat.com>
Deltacloud API, CloudForms