blocks|key|952058|text|您可能需要查看RabbitMQ。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|952059|entityMap|0|LINK|mutability|MUTABLE|url|http://www.rabbitmq.com/^0|7|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You might want to look into <a href="http://www.rabbitmq.com/" rel="noreferrer">RabbitMQ</a>.

blocks|key|2366676|text|我们使用RTI+DDS实现。它需要花费$$，但它支持许多服务质量参数。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2366677|有一个名为OpenDDS的免费直接合成实现，但我没有使用它。|2366678|如果目标语言是静态类型的，我看不出您如何才能避免预先定义数据类型的需要。|2366679|entityMap|0|LINK|mutability|MUTABLE|url|http://www.rti.com/products/dds/index.html|1|http://www.ociweb.com/products/opendds^0|4|7|0|0|5|7|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

We use the <a href="http://www.rti.com/products/dds/index.html" rel="nofollow noreferrer">RTI DDS</a> implementation. It costs $$, but it supports many quality of service parameters.

There is a free DDS implementation called <a href="http://www.ociweb.com/products/opendds" rel="nofollow noreferrer">OpenDDS</a>, but I've not used it.

I don't see how you can get around the need to predefine your data types if the target language is statically typed.

blocks|key|2366702|text|深入了解各种JMS实现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2366703|它们中的大多数不仅仅是Java，它们还为其他语言提供客户端库。|2366704|Suns+OpenMQ至少有一个C%2B%2B接口，ActiveMQ为许多公共语言提供客户端库。|2366705|当涉及消息格式时，它们通常与消息中间件本身分离。您可以定义自己的消息格式。您可以定义自己的XML架构并发送XML消息。如果您愿意，可以使用某个3方库发送BER编码的ASN.1。或者用JSON库格式化和解析数据。|2366706|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Look a bit deeper into the various JMS implementations.

Most of them are not Java only, they provide client libraries for other languages too.

Suns OpenMQ have at least a C++ interface, Apache ActiveMQ provides client side libraries for many common languages.

When it comes to message formats, they're usually decoupled from the message middleware itself. You could define your own message format. You could define your own XML schema and send XML messages. You could send BER encoded ASN.1 using some 3. party library if you want.
Or format and parse the data with a JSON library.

blocks|key|2366764|text|你可以看看PubSubHubbub。它是Atom/RSS的扩展，可以通过web挂钩来分配pubsub。接口是HTTP和XML，因此它与语言无关。随着Google、FriendFeed和FeedBurner正在使用它，它越来越多地被采用。主要的用例是博客和其他东西，但是当然你可以有任何类型的有效负载。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2366765|到目前为止，我所知道的唯一的开源实现是Google的这一个。他们说对自我托管的支持即将到来。|2366766|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/PubSubHubbub|1|http://code.google.com/p/pubsubhubbub/^0|5|C|0|0|Q|3|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

You might take a look at <a href="http://en.wikipedia.org/wiki/PubSubHubbub" rel="nofollow noreferrer">PubSubHubbub</a>. It's a extension to Atom/RSS to alow pubsub through webhooks. The interface is HTTP and XML, so it's language-agnostic. It's gaining increasing adoption now that Google Reader, FriendFeed and FeedBurner are using it. The main use case is blogs and stuff, but of course you can have any sort of payload.

The only open source implementation I know of so far is <a href="http://code.google.com/p/pubsubhubbub/" rel="nofollow noreferrer">this one</a> for the Google AppEngine. They say support for self-hosting is coming.

blocks|key|2366816|text|你可能对肌肉库感兴趣(免责声明:我写的，所以我可能有偏见)。我认为它符合你规定的所有标准。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2366817|https://public.msli.com/lcs/muscle/|offset|length|2366818|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|Z|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

You might be interested in the MUSCLE library (disclaimer: I wrote it, so I may be biased). I think it meets all of the criteria you specified.

<a href="https://public.msli.com/lcs/muscle/" rel="nofollow noreferrer">https://public.msli.com/lcs/muscle/</a>

blocks|key|840680|text|还有OpenSplice数字频率合成器。这一个类似于RTI的直接数字频率合成，除了它是LGPL！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|840681|查看它：|840682|entityMap|0|LINK|mutability|MUTABLE|url|http://www.opensplice.org/^0|17|1|0|2|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

There is also OpenSplice DDS. This one is similar to RTI's DDS, except that it's LGPL! 

Check <a href="http://www.opensplice.org/" rel="nofollow noreferrer">it</a> out:

blocks|key|840732|text|正如前面的文章指出的，您的选项之一是OpenSplice+DDS，它是OMG标准的开源实现(NDDS实现的相同标准)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|840733|与您正在考虑的其他中间件相比，OpenSplice的主要优点可以概括为：|840734|性能|unordered-list-item|840735|对QoS的丰富支持(持久性、容错性、及时性等)|840736|数据中心(例如查询和过滤数据流的可能性)|840737|我想了解的是你对IDL有什么问题。DDS使用IDL作为独立于语言的方式来指定用户数据类型.但是DDS并不局限于IDL，如果您愿意的话，您可以使用XML。指定数据类型并将它们的表示形式与特定的编程语言分离的优点是中间件可以：|840738|(1)免除序列化数据的负担，|840739|(2)产生非常有效的时间/空间序列化，|840740|(3)确保端到端类型的安全，|840741|(4)允许对整个数据类型(不仅仅是JMS中的标头)进行内容过滤，|840742|(5)启用跨编程语言(如Java、C/C%2B%2B、C#等)的联机互操作性。|840743|根据您正在设计的系统或应用程序，上面的一些属性可能并不有用/相关。在这种情况下，您可以简单地生成一个，几个，"DDS类型“，这是您的序列化数据持有人。|840744|如果考虑到JMS，它为您提供了5种不同的主题类型，您可以使用这些主题类型发送数据。使用DDS，您也可以这样做，但您可以灵活地准确地定义主题类型。|840745|最后，您可能需要查看Scala和DDS上的这个博客条目，以便更详细地讨论类型和静态类型为什么是好的，特别是在分布式系统中。|offset|length|840746|-AC|840747|entityMap|0|LINK|mutability|MUTABLE|url|http://bit.ly/9soTyY^0|0|0|0|0|0|0|0|0|0|0|0|0|0|L|6|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1F|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1G|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|1H|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|1I|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1J|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1K|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1M|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1N|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1O|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1P|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1R|8|@]|9|@$12|1S|13|1T|1|1U]]|A|$]]|$1|14|3|15|5|6|7|1V|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]]|17|$18|$5|19|1A|1B|A|$1C|1D]]]]

As pointed-out by an earlier post in this thread, one of your options is OpenSplice DDS which is an Open Source implementation of the OMG DDS Standard (the same standard implemented by NDDS). 

The main advantages of OpenSplice DDS over the other middleware you are considering can be summarized as:

<ul>
<li>Performance</li>
<li>Rich support for QoS (Persistence, Fault-Tolerance, Timeliness, etc.)</li>
<li>Data Centricity (e.g. possibility of querying and filtering data streams)</li>
</ul>

Something that I'd like to understand is what are your issues with IDL. DDS uses IDL as language-independent way of specifying user data types. However DDS is not limited to IDL, you could be using XML, if you prefer. The advantage of specifying your data types, and decoupling their representation from a specific programming language, is that the middleware can:

(1) take away from you the burden of serializing data, 

(2) generate very time/space efficient serialization, 

(3) ensure end-to-end type safety, 

(4) allow content filtering on the whole data type (not just the header like in JMS), and 

(5) enable on-the wire interoperability across programming languages (e.g. Java, C/C++, C#, etc.)

Depending on the system or application you are designing, some of the properties above might not be useful/relevant. In that case, you can simply generate one, a few, "DDS Type" which is the holder of you serialized data.

If you think about JMS, it provides you with 5 different topic types you can use to send your data. With DDS you can do the same, but you have the flexibility to define exactly the topic types. 

Finally, you might want to check out <a href="http://bit.ly/9soTyY" rel="nofollow noreferrer">this blog entry</a> on Scala and DDS for a longer discussion on why types and static-typing are good especially in distributed systems.

-AC

blocks|key|840789|text|我用过的三个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|840790|IBM系列-太贵了，很难使用。|unordered-list-item|840791|(改名为EMS?)是非常快，使用UDP，也可以使用没有中央服务器。我最喜欢的，但很贵，需要一笔主干费。|840792|ActiveMQ+--我目前正在使用它，但发现它经常崩溃。此外，它还需要一些像spring.net这样的从Java移植的项目。它可以工作，但由于稳定性问题，我不能推荐它。|840793|还使用了MSMQ来构建我自己的Pub/Sub，但是由于它不能直接处理它，所以您需要编写大量的代码。|840794|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

Three I've used:

<ul>
<li>IBM MQ Series - Too Expensive, hard to work with. </li>
<li>Tico Rendezvous - (renamed now to EMS?) Was very fast, used UDP, could also be used with no central server. My favorite but expensive and requires a maint fee.</li>
<li>ActiveMQ - I'm using this currently but finding it crashes frequently. Also it's requires some projects ported from Java like spring.net. It works but I can't recommend it due to stability issues.</li>
</ul>

Also used MSMQ in an attempt to build my own Pub/Sub, but since it doesn't handle it out of the box your stuck writing a considerable amount of code.

blocks|key|840813|text|，如果您在公司级别上工作，许可证并不太昂贵。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|840814|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|$]]

IBM Webpshere MQ, and the licence is not too expnsive if you work on a corporate level.

I'm in the market for a good open source network based Pub/Sub (observer pattern) library. I haven't found any I like:

<ul>
<li>JMS - tied to Java, treats message contents as dumb binary blobs</li>
<li>NDDS - $$, use of IDL</li>
<li>CORBA/ICE - Pub/Sub is built on-top of RPC, CORBA API is non-intuitive</li>
<li>JBOSS/ESB - not too familiar with</li>
</ul>

It would be nice if such a package could to the following:

<ul>
<li>Network based</li>
<li>Aware of payload data, users should not have to worry about endian/serialization issues</li>
<li>Multiple language support (C++, ruby, Java, python would be nice)</li>
<li>No auto-generated code (no IDLs!)</li>
<li>Intuitive subscription/topic management</li>
</ul>

For fun, I've <a href="http://github.com/topgun300/psxml/tree/master" rel="noreferrer">created my own</a>. Thoughts?

Best Publish/Subscribe "Middleware"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在市场上寻找一个良好的开源网络，基于Pub/Sub (观察者模式)库。我还没找到我喜欢的：JMS -绑定到Java，将消息内容视为哑二进制blobs。NDDS - $$，使用IDLCORBA/ICE - Pub/Sub是建立在RPC之上的，CORBA API是不直观的。JBOSS/ESB -不太熟悉如果这样一套方案...

问最佳发布/订阅“中间件”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问最佳发布/订阅“中间件”EN