[rabbitmq-discuss] Making persistence simpler (Was: AMQP & Python Write-Up)

Holger Hoffstätte holger at wizards.de
Sat Jan 17 18:25:10 GMT 2009

Martin Sustrik wrote:
> Specifying persistence on per-message basis makes no sense of course. 

"Of course"? I'd like to hear why you think that is so obvious, because I
don't think it is. :)
Explicitly required persistence can be seen as just another orthogonal
property to transactionality, lifetime or other QoS requirements.
Enforcing these properties for every consumer up-front might admittedly
make the life of a broker implementer easier, but at the cost of going
against the client-driven nature and an architecture with intelligent and
responsible endpoints (bottom up). You can always superimpose centralized
decisions over this (e.g. through consistent configuration), but not the
other way.


More information about the rabbitmq-discuss mailing list