IntroductionA messaging broker in my opinion should be fairly easy to write. I happened to come across a proposed messaging standard (yet another!) called Advanced Message Queue Protocol. Apparently Apache's ActiveMQ, Qpid and Red hat messaging already implement the protocol.
The target users of the project are enterprise high reliability messaging who can scale the hardware if needed to scale performance.
The projectGoalsThe kernel would simply implement the core concepts of AMQP. Namely, Exchanges, Queues, Bindings and Routing. The kernel should hardly change as the protocol matures. So, it is critical to ensure only the core concepts are embedded in the kernel. As this will be the heart of the messaging system performance is a key. Persistence would be implemented at kernel strictly using Java Persistance API. This should give us a choice between multiple DB vendors. As a feature, the kernel would provide an option to disable persistence. This feature should provide high-throughput messaging for non-sensitive, perishable data. FAQMessaging broker? Are you not re-inventing the wheel?May be I am. But it is fun to do your own thing sometime. Dont you agree? May be I would end up making a square shaped wheel that works better than your circular ones.
