blocks|key|1153611|text|出于互操作性的考虑，请使用web服务。在Java世界之外，JMS很少使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1153612|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For interoperability sake, use a web service. JMS is little used outside the Java world.

blocks|key|1153637|text|检查链接|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1153638|difference+between+using+JMS/Messaging+Middleware+versus+Web+services+|offset|length|1153639|Messaging,+JMS+and+Web+Services|1153640|Web+Services+HTTP+vs.+JMS+|1153641|Choosing+among+JCA,+JMS,+and+Web+services|1153642|Java+Message+Service|1153643|Web+service|1153644|因此，如果通信应用程序是基于Java的，使用JMS，如果可能是不同的，那么Web服务...这就是我所遵循的。|1153645|entityMap|0|LINK|mutability|MUTABLE|url|http://searchsoa.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid26_gci857436,00.html|1|http://www.ebizq.net/topics/messaging_middleware/features/1541.html|2|http://it.toolbox.com/blogs/the-soa-blog/web-services-http-vs-jms-19110|3|http://www.ibm.com/developerworks/webservices/library/ws-jcajms.html|4|http://en.wikipedia.org/wiki/Java_Message_Service|5|http://en.wikipedia.org/wiki/Web_service^0|0|0|1Y|0|0|0|V|1|0|0|Q|2|0|0|15|3|0|0|K|4|0|0|B|5|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@$D|1B|E|1C|1|1D]]|A|$]]|$1|F|3|G|5|6|7|1E|8|@]|9|@$D|1F|E|1G|1|1H]]|A|$]]|$1|H|3|I|5|6|7|1I|8|@]|9|@$D|1J|E|1K|1|1L]]|A|$]]|$1|J|3|K|5|6|7|1M|8|@]|9|@$D|1N|E|1O|1|1P]]|A|$]]|$1|L|3|M|5|6|7|1Q|8|@]|9|@$D|1R|E|1S|1|1T]]|A|$]]|$1|N|3|O|5|6|7|1U|8|@]|9|@$D|1V|E|1W|1|1X]]|A|$]]|$1|P|3|Q|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]|Z|$5|U|V|W|A|$X|10]]|11|$5|U|V|W|A|$X|12]]|13|$5|U|V|W|A|$X|14]]|15|$5|U|V|W|A|$X|16]]|17|$5|U|V|W|A|$X|18]]]]

check the links

<a href="http://searchsoa.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid26_gci857436,00.html" rel="nofollow noreferrer">difference between using JMS/Messaging Middleware versus Web services </a>

<a href="http://www.ebizq.net/topics/messaging_middleware/features/1541.html" rel="nofollow noreferrer">Messaging, JMS and Web Services</a>

<a href="http://it.toolbox.com/blogs/the-soa-blog/web-services-http-vs-jms-19110" rel="nofollow noreferrer">Web Services HTTP vs. JMS </a>

<a href="http://www.ibm.com/developerworks/webservices/library/ws-jcajms.html" rel="nofollow noreferrer">Choosing among JCA, JMS, and Web services</a>

<a href="http://en.wikipedia.org/wiki/Java_Message_Service" rel="nofollow noreferrer">Java Message Service</a>

<a href="http://en.wikipedia.org/wiki/Web_service" rel="nofollow noreferrer">Web service</a>

So if communicating Applications are Java based use JMS and if may be different then Web services... thats what which I follow.

blocks|key|1153708|text|JMS是一种抽象消息传递中间件的应用编程接口，如ActiveMQ或IBM+MQSeries。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1153709|消息传递中间件具有存储转发范例和异步消息传递，而web服务倾向于促进同步过程调用范例。在许多可能出错的分布式系统中，当系统的一部分不可用或性能不佳时，异步处理往往会将注意力更好地集中在需要做的事情上，而处理这些事情所需的代码往往会简单得多。|1153710|如果你有多个服务器在监听同一个队列，集群部分就变得微不足道了，在这种情况下，并行和负载平衡是免费的。|1153711|就我个人而言，我发现JMS比web服务更容易使用，也更健壮和可靠，但消息传递中间件必须支持您想要使用的所有平台。如果所有需要相互通信的组件都在您的控制之下，我会认真考虑使用具有JMS接口的消息传递中间件。|1153712|如果另一方是外部的，那么很可能是Web服务规则，在这种情况下，您可以考虑使用薄层将外部web服务转换为内部消息传递基础结构，以便您仍然具有大多数优势。|1153713|如果它只是“在webapp上打一个远程API”，那么它当然也不会为设置异步消息而付出代价。|1153714|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

JMS is an API which abstracts messaging middleware, like ActiveMQ or IBM MQSeries. 

Messaging middleware has a store-and-forward paradigm and asynchronous message passing, while web services tend to promote a synchronous procedure calling paradigm. In distributed systems where a lot can go wrong, dealing with things asynchronously tend to focus the mind better to the things you need to do when part of the system is not available or poorly performing and the code needed to deal with that tends to be a lot less complicated.

Clustering parts become trivial if you have multiple servers listening on the same queue, parallelism and load balancing is for free in this case.

Personally I find JMS much easier to work with and more robust and reliable than web services, but the messaging middleware must support all platforms you want to use. If all the components who need to talk to each other are under your control, I would give a messaging middleware with a JMS interface serious consideration.

If the other party is external then probably Web Services rule, and in that case you could think of a using thin layer to convert the external web service to an internal message passing infrastructure so you still have the most of the advantages.

If it is "just slapping an remote API on a webapp" then of course it does not pay either to setup asynch messaging.

blocks|key|939441|text|您可以根据您的互操作性、规模、分布和集成需求来使用这两者。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|939442|使用SOAP、XML+RPC和REST的Web服务方法在使用HTTP作为协议的情况下提供了一些非常可互操作的东西。在服务端，您可能会收到web服务请求，然后将其编组到消息中。然后，您的消息可以传递到消息传递总线。|939443|JMS是与消息总线接口的一个合理的应用编程接口，我发现Active/MQ在这里非常好。Active/MQ支持跨多种语言的JMS。|offset|length|939444|通过消息传递，您可以利用请求/回复企业集成模式来接收响应，并通过您的web服务返回它们。但是，考虑一下提供关于订单是否已处理的即时反馈与反馈订单已收到的事实的优点；您可能不需要实现请求/回复来确认订单已收到。|939445|消息传递的好处可以在这里找到：http://www.eaipatterns.com/Messaging.html|939446|您甚至可能希望使用Apache+Camel来简化高度可伸缩的分布式服务层的开发。|939447|entityMap|0|LINK|mutability|MUTABLE|url|http://activemq.apache.org/|1|http://www.eaipatterns.com/Messaging.html|2|http://camel.apache.org/^0|0|0|R|9|0|0|0|F|15|1|0|9|C|2|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@$F|12|G|13|1|14]]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@$F|17|G|18|1|19]]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@$F|1B|G|1C|1|1D]]|A|$]]|$1|N|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]|X|$5|Q|R|S|A|$T|Y]]]]

You can use both depending on your interoperability, scale, distribution and integration requirements. 

Web service approaches utilising SOAP, XML RPC and REST provide something quite interoperable given the use of HTTP as the protocol. From a service side, you might receive a web service request and then marshal it into a message. Your message could then be delivered to a messaging bus.

JMS is a reasonable API for interfacing with a messaging bus and I've found that <a href="http://activemq.apache.org/" rel="noreferrer">Active/MQ</a> very good here. Active/MQ supports JMS across many languages. 

With messaging you can utilise the Request/Reply Enterprise Integration Pattern to receive responses and return them via your web service. However think about the merit of providing immediate feedback as to whether the order has been processed vs feeding back the fact that an order has been received; you might not need to implement request/reply to acknowledge that an order has been received.

The benefits of messaging can be found here: <a href="http://www.eaipatterns.com/Messaging.html" rel="noreferrer">http://www.eaipatterns.com/Messaging.html</a>

You may even want to look at <a href="http://camel.apache.org/" rel="noreferrer">Apache Camel</a> to simplify the development of highly scalable and distributed service layers.

I need to develop a system which accepts orders and returns confirmation. Orders could come from java or non java clients. 

Not sure whether to go for web service implementation or JMS. 

Any suggestions ...

Difference between JMS and Web Service

中间件

服务器

Java

我需要开发一个系统，接受订单和返回确认。订单可以来自java或非java客户端。不确定是使用web服务实现还是使用JMS。任何建议..。

问JMS与Web服务的区别
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JMS与Web服务的区别EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JMS与Web服务的区别
EN