Rob Davies and I spent some time last week looking at his Kaha message store implementation. In a way, it’s similar to a experimental QuickJournal implementation that I had committed previously. The idea of the QuickJournal was that Journal log files were not deleted and that messages could be easily retrieved from the Journal. The journal would only checkpoint to the long term store the location of where the messages are located in the journal.

I exposed the gigantic destination issues that ActiveMQ has in a previous blog post. I’ll take a little time to expand on the issue and why it’s not simple to solve, and what ActiveMQ 4.0 does today.

One of the current issues with ActiveMQ is that it’s an uber fast message broker while consumers are online and consuming messages, but things start to kinda not works so great when you have a use case where you want to queue up ‘work/messages’ for a consumer that will be offline for days.