Messaging tends to concentrate on the reliable exchange of messages around a network; using queues as a reliable load balancer and topics to implement publish and subscribe. An ESB typically tends to add different features above and beyond messaging such as orchestration, routing, transformation and mediation. I’d recommend reading about the Enterprise Integration Patterns which … Read more
A standard that I’ve followed in the past is to use web services when the key requirement is speed (and data loss isn’t critical) and messaging when the key requirement is reliability. Like you’ve said, if the receiving system is down, a message will sit on a queue until the system comes back up to … Read more
Please check this one (Wayback Machine link used as article went offline since 2020) With AUTO_ACKNOWLEDGE mode the acknowledgment is always the last thing to happen implicitly after the onMessage() handler returns. The client receiving the messages can get finer-grained control over the delivery of guaranteed messages by specifying the CLIENT_ACKNOWLEDGE mode on the consuming … Read more
I’m using it for research, so “semi-production”. It’s a wonderful framework, and the way things are architected certainly make sense once you fully grok it. But I’ve hit far too many problems to consider it production ready. I’m using jzmq, so some of this might be specific to that. Setting up jzmq on OS X … Read more
May not be “best practice” advice here… but based on real life needs and experience: we have distributed system, 60 boxes running each 10 clients all do task X, and they need to take the next task from a queue. The queue is being fed from one other “client”… We had used inter process communication, … Read more
Although ESB is based on messaging, it is not “just” messaging and not just a buzzword. So if you start with plain old async messaging, the early networks tended to be very point-to-point. You had to wire up (i.e. configure through some admin interface) each connection and each pair of destinations and if you dared … Read more
Data24-7 offers an API for looking up the carrier for wireless phone numbers. It also returns the email addresses to send SMS and MMS messages to the phone. It’s not free, it’s $12 per month and $0.006 per lookup. The link is: http://www.data24-7.com
The standard JMS API is merely a set of interfaces; JMS providers (such as WebSphere MQ) provide their own implementations for these interfaces. The only thing that you can say for sure about all JMS implementations is that they all adhere to the JMS API; other than that, a JMS implementation may use any protocol … Read more
I didn’t read the article, so I can only speculate what he can mean exactly, but as he gives ESB as an example against microservices and ZeroMQ as an example for micro services I hope my speculation will be pretty exact: One of the ideas of Unix (and Linux) is to build small independent applications … Read more