CloudAMQP vs Kafka vs apache nifi

CloudAMQP vs Kafka: What are the differences?

Developers describe CloudAMQP as "RabbitMQ as a Service". Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms. On the other hand, Kafka is detailed as "Distributed, fault tolerant, high throughput pub-sub messaging system". Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

CloudAMQP and Kafka can be primarily classified as "Message Queue" tools.

Some of the features offered by CloudAMQP are:

• Support - 24/7 support, via email, chat and phone.
• Real time metrics and alarms - Get notified in advanced when your queues are growing faster than you're consuming them, when you're servers are over loaded etc. and take action before it becomes a problem.
• Auto-healing - Our monitoring systems automatically detects and fixes a lot of problems such as kernel bugs, auto-restarts, RabbitMQ/Erlang version upgrades etc.

On the other hand, Kafka provides the following key features:

• Written at LinkedIn in Scala
• Used by LinkedIn to offload processing of all page and other views
• Defaults to using persistence, uses OS disk cache for hot data (has higher throughput then any of the above having persistence enabled)

"Some of the best customer support you'll ever find" is the primary reason why developers consider CloudAMQP over the competitors, whereas "High-throughput" was stated as the key factor in picking Kafka.

Kafka is an open source tool with 13.1K GitHub stars and 6.99K GitHub forks. Here's a link to Kafka's open source repository on GitHub.

According to the StackShare community, Kafka has a broader approval, being mentioned in 691 company stacks & 2398 developers stacks; compared to CloudAMQP, which is listed in 17 company stacks and 15 developer stacks.