嵌入ActiveMQ与独立性能(ActiveMQ embedded vs standalone performance)

嵌入ActiveMQ与独立性能(ActiveMQ embedded vs standalone performance)

我们有一个遗留系统，其中ActiveMQ被配置为一个JVM中主应用程序的一部分。 它已经使用tcp传输配置如下

<transportConnector name="tcp" uri="tcp://0.0.0.0:61616?wireFormat.tcpNoDelayEnabled=true&amp;wireFormat.tightEncodingEnabled=false" />

我们想改变架构并将ActiveMQ分离成独立的JVM; 关于进程内消息与进程外消息之间存在一些争论。 这样做对性能有影响吗？

（当然我们会做性能测试来回顾这个方法）

We have a legacy system where ActiveMQ configured as part of the main app within one JVM. Its already configured using tcp transport as follows

<transportConnector name="tcp" uri="tcp://0.0.0.0:61616?wireFormat.tcpNoDelayEnabled=true&amp;wireFormat.tightEncodingEnabled=false" />

We would like to change the architecture and separate ActiveMQ into a standalone JVM; There is some debate about in-process vs. out of process messaging. Is there any impact in term of performance by doing that?

(Of course we will do performance test to review this approach)

最满意答案

您已经通过TCP进行通信，而不是VM /内存传输，因此应该没有性能差异。

嵌入式代理中使用的VM传输可能会更高性能。

You already have communication through TCP rather than the VM/in-memory transport so there should be no difference in performance.

The VM transport used in an embedded broker will probably be more performant.