[rabbitmq-discuss] Custom storage backends for queues (MySQL)
jon at jbrisbin.com
Tue Jan 18 14:29:57 GMT 2011
On Jan 15, 2011, at 11:14 AM, Jerry Kuch wrote:
> If a plugin for your store of choice doesn't exist, then one writes a storage plugin, in Erlang, by implementing the rabbit_backing_queue behaviour, which effectively makes up the storage API, and talks to the storage system of your choice.
A couple quick questions about this:
Should a replacement rabbit_backing_queue be packaged as a regular plugin?
How would I configure the broker to use my own storage module?
Should one start with rabbit_variable_queue.erl and replace only the bits that talk to the message store (leaving the memory management logic intact) as a first step?
It would probably be a good idea to look at the content type of the message to figure out how to store it in the backing store, right (which would open the possibility of working with message data independently of the broker by interrogating its contents)?
Would it be a bad idea to have store-side code as part of the storage system? In particular, I'm thinking about having Erlang-language M/R code or event triggers which would need to be installed into the server (Riak in this case) to manage indexes and metadata. In general, I don't like the idea of having to install things in more than one place. It would probably make some things considerably easier (and more performant), though.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss