Bug 329792

Description Gunnar Wagenknecht 2010-11-09 09:32:44 EST

We need a queue service in Gyrex which allows to create queues, submit messages to and retrieve messages from them. Together The service must not define any strong guarantees but must allow to cover implementations based on Amazon SQS,  OpenStack, RabbitMQ, etc. 

Thus, the API might be very rich but offer enough feature in order to support the following thing:

* declare queue
Ensures that a queue exists (creates it if necessary)

* publish message
Publishes a message (set of bytes)

* message consumer callback
Allows to add message consumers (callback interface that will receive one message at a time; actually returns a message consumer registration handle which can be used to remove a consumer callback)


A few notes:

Queue management is left to the actual queue service implementation which should likely expose it's own queue management interface.

No guarantees are given regarding message delivery/ordering other than the guarantees given by the underlying implementations.

The queue service is *not* a distributed event bus.