[openamq-dev] Persistence

Carl Bourne cbourne at intellect.co.uk
Tue Apr 3 13:54:19 CEST 2007


Pieter,

Very interesting - Thanks very much for input on this one.

Were not particularly hung up on any particular way of doing things -
actually I like the sound of your approach as it obviously significantly
simplifies the transport mechanism. As Martin says, there's a continuous
danger of creating bloat ware. 

My goal is to select a standards based platform that minimizes the work
involved with reliably getting data from A to B. Thus, we can focus 100
percent in the area where we add our value.  

I'm in the early stages of investigating this technology and trying to
get my head around the different variants. Do you have anything that
describes/demonstrates how you achieve end to end persistence?

Regards,

Carl






-----Original Message-----
From: openamq-dev-bounces at lists.openamq.org
[mailto:openamq-dev-bounces at lists.openamq.org] On Behalf Of Pieter
Hintjens
Sent: 03 April 2007 12:25
To: OpenAMQ development discussion
Subject: Re: [openamq-dev] Persistence

Carl,

> Are there any plans to support persistent messaging within OpenAMQ at
some
> stage?

Our view of reliability is somewhat different from that of other AMQP
implementations.  The classic design is to implement persistence in
the broker, and to use transactions between the clients and the broker
to govern how messages are persisted.

Doing this properly also means implementing clustering with full
failover.  This gets very difficult, and it's one of the reasons the
AMQP spec is getting fatter and more complex that I'd like.

Also, classic reliability does not work across multi-broker
architectures; that is, you can lose messages once your network gets
more complex, even if you have fully-reliable brokers in most of it.

So our architecture - which is still being worked on - treats the
brokers as unreliable, and does end-to-end persistence from client to
client.  This is how we implemented reliability in our production work
for JPMC, it's much simpler than using persistence in the broker.

Overall, OpenAMQ is targetting the very high performance sector, and
we'll be releasing support for multicast and end-to-end reliability
when - as Martin says - we get concrete clients for these
technologies.

-Pieter
_______________________________________________
openamq-dev mailing list
openamq-dev at lists.openamq.org
http://lists.openamq.org/mailman/listinfo/openamq-dev


More information about the openamq-dev mailing list