While someone may know a tool to test them all I'd recommend that you build a testing scenario that resembles your intended use (message sized, integration patterns (e.g. do you need CBR and if so what), required latencies, message rates, target environment etc.) Synthetic benchmarks can be misleading and will most likely not represent your usage scenario
As a side note I'd say that AMQP has the advantage that it also defines the wire protocol so if you choose one you can change the backend without affecting the client
发布评论
评论（2）
虽然有人可能知道一个工具来测试所有这些，但我建议您构建一个类似于您的预期用途的测试场景（消息大小、集成模式（例如，您是否需要 CBR，如果需要的话，需要什么）、所需的延迟、消息速率、目标环境等）
综合基准可能会产生误导，并且很可能无法代表您的使用场景
作为旁注，我想说 AMQP 的优点是它还定义了有线协议，因此如果您选择一个，您可以更改后端而不影响客户端
While someone may know a tool to test them all I'd recommend that you build a testing scenario that resembles your intended use (message sized, integration patterns (e.g. do you need CBR and if so what), required latencies, message rates, target environment etc.)
Synthetic benchmarks can be misleading and will most likely not represent your usage scenario
As a side note I'd say that AMQP has the advantage that it also defines the wire protocol so if you choose one you can change the backend without affecting the client
SPEC JMS 2007 怎么样？我认为这对你的情况非常有用:)
What about SPEC JMS 2007 ??? I think it would be quite usefull for your case :)