This is not actually entirely new - this was something that I thought of about an year or so ago and then put on hold due to the fact that I was working on something similar on my job and did not want to mix the two.
The idea is simple - we use JMS as a messaging backbone for enterprises. A lot of boiler plate code needs to be written to connect and publish/subscribe messages from the JMS server. Of course our life is made easy by frameworks like Spring that make it easy to ignore the low level stuff and just publish messages. However, these miss certain value add features like
- Automatic application level message sequence numbering
- Checking message sequencing (This does not make sense in JMS in most cases).
- Publisher heart beat - is the publisher alive or not?
I am still coming up with ideas and fleshing the thing out.
The only thing that is certain at this point is that I have started this project in out and out TDD mode (as against my usual urge to go straight to code and test lazily) and am using Netbeans, with ActiveMQ for my local testing.
I have only managed to write and test two classes today - should commit something by new year.
0 comments:
Post a Comment