简体   繁体   English

ActiveMQ 与 JMS

[英]ActiveMQ vs JMS

I am trying to understand JMS.我正在尝试了解 JMS。

What is the difference between ActiveMQ and JMS ActiveMQ 和 JMS 有什么区别

can pool the data from NON ActiveMQ with ActiveMQ plugin in Spring?可以在 Spring 中使用 ActiveMQ 插件池来自非 ActiveMQ 的数据吗?

Thanks ,In advance提前致谢

JMS is a specification. JMS 是一种规范。 JMS has three main parts to it. JMS 具有三个主要部分。 The first is the producer , which is nothing more than a bean that submits a "message" to a JMS broker (#2) (the system that manages messages between producers and consumers ).第一个是生产者,它只不过是一个向 JMS代理(#2)(管理生产者消费者之间的消息的系统)提交“消息”的 bean。 In this case, ActiveMQ is the broker.在这种情况下,ActiveMQ 是代理。 Once the broker receives a message, the consumer (#3), or Message-Driven Bean (MDB), processes the message.一旦代理收到消息,消费者(#3)或消息驱动 Bean (MDB) 就会处理该消息。

If you want to work with JMS, you'll just write both your producer/consumer code using the JMS API, but behind the scenes there is a "resource adapter" that is a special ActiveMQ driver that will connect to an ActiveMQ instance and do the management for you.如果您想使用 JMS,您只需使用 JMS API 编写生产者/消费者代码,但在幕后有一个“资源适配器”,它是一个特殊的 ActiveMQ 驱动程序,它将连接到 ActiveMQ 实例并执行为您管理。

Have a look at this post I made recently .看看我最近发表的这篇文章 I'm still trying to figure out the best way to write JMS beans, but I've got the basics down.我仍在尝试找出编写 JMS bean 的最佳方法,但我已经掌握了基础知识。

The accepted answer emphasizes what is the structure of JMS is.接受的答案强调了 JMS 的结构是什么。 Not disagreeing just want to add to it in case anyone else wants to know.不是不同意,只是想补充一下,以防其他人想知道。 ActiveMQ could be a JMS supplier. ActiveMQ可以是JMS供应商。 A JMS supplier shapes the computer program system for encouraging the utilize of JMS concepts interior an application. JMS供应商塑造了计算机程序系统,以鼓励在应用程序内部使用 JMS 概念。 A single node of ActiveMQ which permits clients to associate to it and utilize these informing concepts is called an "ActiveMQ Broker."允许客户端关联并利用这些通知概念的 ActiveMQ 的单个节点称为“ActiveMQ 代理”。 Enterprises feel this disparity with business actions such as mergers and acquisitions.企业通过并购等商业行为感受到了这种差异。 This creates the need to maintain an increasingly heterogeneous collection of business applications.这就产生了维护日益异构的业务应用程序集合的需要。 As your enterprise grows, so does the need to allow all of these platforms to share data.随着企业的发展,允许所有这些平台共享数据的需求也在增长。 A number of architectural patterns exist today which help to solve this problem.当今存在的许多架构模式有助于解决这个问题。

Some other examples of JMS providers are: JMS 提供程序的其他一些示例是:

  • HornetQ.大黄蜂Q。
  • RabbitMQ.兔子MQ。
  • SonicMQ. SonicMQ。
  • Winsows Azure Messaging Winsows Azure 消息传递

The following example shows a simple configuration of an ActiveMQ connection:以下示例显示了 ActiveMQ 连接的简单配置:

<jms:config name="JMS_Config">
 <jms:active-mq-connection >
  <jms:factory-configuration brokerUrl="tcp://localhost:61616" />
 </jms:active-mq-connection>
</jms:config>

This post explains a detailed difference between the ActiveMQ and JMS (or maybe about the details of their specifications).这篇文章解释了ActiveMQ 和 JMS之间的详细区别(或者可能是关于它们规范的细节)。 Hope it clears your concepts.希望它能清除你的概念。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM