ActiveMQ vs Apollo vs Kafka [英] ActiveMQ vs Apollo vs Kafka
问题描述
我以前没有任何使用 *MQ 的经验，我希望在一般情况下建立有关 JMS 和消息队列的知识.这样，我想知道我是应该从 ActiveMQ 开始还是完全忽略"它并从自学 Apollo 开始.Apollo 和 ActiveMQ 一样功能齐全吗?它是否实现了 JMS 2.0(我看到 ActiveMQ 被 1.1 卡住了)?我会不会遗漏一些非常重要的东西?
I don't have any previous experience with *MQs and I'm looking to build knowledge on JMS and message queues in general. That way, I wonder whether I should start with ActiveMQ or just "ignore" it altogether and start by teaching myself Apollo. Is Apollo as feature-complete as ActiveMQ? Does it implement JMS 2.0 (I see that ActiveMQ got stuck with 1.1)? Will I be missing something really important?
另外，Kafka 与这两种解决方案相比如何?
Also, how does Kafka compare to these two solutions?
推荐答案
Apache ActiveMQ 是一款功能强大且功能强大的工具.它不是最快的 MQ 软件，但对于大多数用例来说已经足够快了.功能包括灵活的集群、故障转移、与不同应用服务器的集成、安全性等.
Apache ActiveMQ is a great workhorse full of features and nice stuff. It's not the fastest MQ software around but fast enough for most use cases. Among features are flexible clustring, fail-over, integrations with different application servers, security etc.
Apache Apollo 是一个尝试，为 ActiveMQ 编写一个新的核心来应对大量的客户端和消息.它没有 ActiveMQ 的所有漂亮和方便的功能，但扩展性更好.当您为其提供大型多核服务器和数千个并发连接时，Apache Apollo 是一个非常快速的 MQ 实现.它有一个漂亮、简单的用户界面，但不是一刀切"的解决方案.
Apache Apollo is an attempt to write a new core for ActiveMQ to cope with a large amount of clients and messages. It does not have all nice and convenient feature of ActiveMQ but scales a lot better. Apache Apollo is a really fast MQ implementation when you give it a large multi-core server and thousands of concurrent connections. It has a nice, simple UI, but is not a "one-size-fits-all" solution.
似乎正在尝试以 ActiveMQ Artemis 的名义将许多 ActiveMQ 功能与 HornetQ 合并.HornetQ 支持 JMS2.0，所以我粗略的猜测是它很可能出现在 ActiveMQ 6.x 中.
It seems that there is an attempt ongoing to merge a number of ActiveMQ features with HornetQ under the name ActiveMQ Artemis. HornetQ has JMS2.0 support, so my humble guess is that it's likely to appear in ActiveMQ 6.x.
卡夫卡是另一种野兽.这是一个非常简单的消息代理，旨在尽可能快地在多个服务器上扩展持久发布订阅(主题).对于中小型部署，Kafka 可能不是最佳选择.它还具有实现高吞吐量的方法，因此您必须在灵活性方面进行大量交易才能获得高分布式吞吐量.如果您是 MQ 和代理领域的新手，我想 Kafka 有点矫枉过正.另一方面——如果你有一个相当大的服务器集群并且想知道如何通过它推送尽可能多的消息——那就试试 Kafka！
Kafka is a different beast. It's a very simple message broker intended to scale persistent publish subscribe (topics) as fast as possible over multiple servers. For small-medium sized deployments, Kafka is probably not the best option. It also has it's way to do things to achieve the high throughput, so you have to trade a lot in terms of flexibility to get high distributed throughput. If you are new to the area of MQ and brokers, I guess Kafka is overkill. On the other hand - if you have a decent sized server cluster and wonder how to push as many messages as possible through it - give Kafka a spin!
这篇关于ActiveMQ vs Apollo vs Kafka的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
