Web Services and Messaging

What arguments should be used when choosing between web service integration and JMS? I am familiar with the basics of both approaches, but in some cases it is not clear which one would be the best for this situation. I guess I'm looking for a great overview comparison with use cases.

thank

+5
source share
2 answers

JMS is a messaging service. It is asynchronous and 2 directional, i.e. You can write an application that sends and receives messages. But this should be an application, implemented, as a rule, in java. I mean, this cannot be a thin client. And the standard JMS protocol is based on TCP, so it can be blocked by a firewall.

The web service is designed as a transport over HTTP, so it usually sends firewalls. But this is one direction: the client calls the server; the server cannot call the client. He just can respond to customer requests. The web service client (especially the RestFull web service) is very simple, so it can be easily implemented as a thin client (for example, an AJAX client).

+4
source

Good question.

-, :
1. , , .
2. .

, (, Java-):
1. /.
2. .
3. .

+3

All Articles