We are trying to have our own startup, with a middleware application to glue small applications with enterprise legacy systems.for such middle-ware to function properly, we will need some sort of messaging system to make different components talk to each other in a reliable way. the alternatives are:use an existing messaging system, such as 0MQ, jBOSS, WebSphere MQ, etc.build our own messaging system the way we see the problemI am more biased towards the later option for the following reasons:to have more control over our final productto avoid any licensing problems later onto learn about messaging while writing the codeto invent something new, that might cost us lots of $$$ if reused an existing systemWhat would you do if in my shoes?
Write own messaging system vs. utilize existing ones
design;message queue;messaging
Since you are a startup I would say it depends on two things.Do you have any time constraints on this?Will building your own messaging system give you an advantage?I don't know what kind of business your startup is in but in general its best to focus on great user experience in the beginning. The code running in the back may be awful but the user will never know that, he'll just notice if the user interface is easy to use.So given that you have some time constraints, if the messaging system doesn't give you anything that makes a great difference for your application, I would use an existing one.It's tested, it's used and there is a knowledge base.  