[openstack-dev] Oslo messaging vs zaqar
Geoff O'Callaghan
geoffocallaghan at gmail.com
Tue Sep 23 00:30:47 UTC 2014
On 23/09/2014 1:59 AM, "Clint Byrum" <clint at fewbar.com> wrote:
>
> Geoff, do you expect all of our users to write all of their messaging
> code in Python?
>
> oslo.messaging is a _python_ library.
>
> Zaqar is a service with a REST API -- accessible to any application.
No I do not. I am suggesting thaf a well designed, scalable and robust
messaging layer can meet the requirements of both as well as a number of
other openstack servuces. How the messaging layer is consumed isn't the
issue.
Below is what I originally posted.
> > --------
> > It seems to my casual view that we could have one and scale that and
use it
> > for SQS style messages, internal messaging (which could include logging)
> > all managed by message schemas and QoS. This would give a very robust
and
> > flexible system for endpoints to consume.
> >
> > Is there a plan to consolidate?
Tks
Geoff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140923/00cb8308/attachment.html>
More information about the OpenStack-dev
mailing list