Large social media sites benefit from JMS when they engage in global server rollouts, Bruno said. Most of these sites need to roll out servers on such a large scale that reliable messaging may be a challenge. This can be alleviated with JMS. Essentially, any project that needs reliable messaging from endpoints to a central system can use JMS. "It's so widely used that it's hard to pinpoint specific industries," he added.
User roundrobin wrote on the stackoverflow.com message board that he is pleased with how JMS has provided stability over unreliable networks. "The loose coupling, in combination with reliable messaging, produces a stable system landscape," roundrobin wrote. This means that messages are sent as soon as it's technically possible, and larger network problems don't interfere.
However, even with the plethora of uses for JMS, experts still advise staying informed about new trends. The previously mentioned AMQP and MQTT are two protocols that have emerged, and more options are available for messaging, Snyder said. He noted that AKKA in particular looks promising. "It provides concurrency and a message-driven backbone inside framework [and] scales well, using an actor-based pattern," he said. "It's not an explicit messaging-based framework; it builds actors and patterns, and underneath scaling using messaging."
More resources on Java messaging:
Prove your knowledge of JMS with our quiz
Pros and Cons of Java, C++ and Visual Basic
Limitations of Java in enterprise application development