vege - Fotolia

Manage Learn to apply best practices and optimize your operations.

Quiz: Do you know the ins and outs of JMS and a JMS API?

Are you a JMS and JMS API know-it-all? Prove it with our quiz.

Enterprise application developers who want components to be independent so they can easily be replaced will find themselves steering clear of tightly coupled APIs and in the direction of a messaging API. The Java Message Service, or JMS API, is one of the more popular answers available. How much do you know about the background and basic workings of a JMS API? Find out with our seven-question quiz!

About the author:
Maxine Giza is the site editor for and can be reached at

Follow us on Twitter @SearchSOA and like us on Facebook.

This was last published in October 2014

Dig Deeper on API management strategy

Join the conversation

1 comment

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

Answer to the question 3 is false. JMS supports both synchronous and asynchronous communication. One may understand this in two design layers. In the lower layer (API) the message delivery may be done both asynchronously by MessageListener#onMessage() and synchronously using Consumer#receive(). On the application level there are no problems building synchronous (blocking) request reply in addition to asynchronous fire-and-forget interactions. What's more, synchronous request-reply web services can be implemented (within enterprise) over JMS with better network efficiency than over HTTP passing through load balancer.