[rabbitmq-discuss] Message persistence format

Jonathan Brisbin jbrisbin at vmware.com
Mon Feb 14 19:33:20 GMT 2011

I've tracked down some problems I've been having with a Riak-based message persister to not having a properly-constructed #basic_message record to give back to the broker. I see some differences between those returned from a working version of a backing queue versus the ones returned from mine.

I'm wondering, then, if there's some guidance you can give on the way to persist messages outside of an Erlang context. Ideally, one should be able to work with the message content. This means storing the individual pieces that make up a message in various ways (headers/links to metadata documents, etc...). But it's easier if I simply serialize the Erlang term for the message and reconstitute it later. It then has all the internal properties it needs on it, etc...

What are the fewest possible pieces of information I need to construct a valid #basic_message record?


Jon Brisbin
SpringSource (a division of VMware)

Twitter: @j_brisbin

More information about the rabbitmq-discuss mailing list