Pros of DistributedLog

Pros of Kafka

• 126

  High-throughput
• 119

  Distributed
• 92

  Scalable
• 86

  High-Performance
• 66

  Durable
• 38

  Publish-Subscribe
• 19

  Simple-to-use
• 18

  Open source
• 12

  Written in Scala and java. Runs on JVM
• 9

  Message broker + Streaming system
• 4

  KSQL
• 4

  Avro schema integration
• 4

  Robust
• 3

  Suport Multiple clients
• 2

  Extremely good parallelism constructs
• 2

  Partioned, replayable log
• 1

  Simple publisher / multi-subscriber model
• 1

  Fun
• 1

  Flexible

Pros of RabbitMQ

• 234

  It's fast and it works with good metrics/monitoring
• 79

  Ease of configuration
• 59

  I like the admin interface
• 50

  Easy to set-up and start with
• 21

  Durable
• 18

  Intuitive work through python
• 18

  Standard protocols
• 10

  Written primarily in Erlang
• 8

  Simply superb
• 6

  Completeness of messaging patterns
• 3

  Scales to 1 million messages per second
• 3

  Reliable
• 2

  Distributed
• 2

  Supports MQTT
• 2

  Better than most traditional queue based message broker
• 2

  Supports AMQP
• 1

  Clusterable
• 1

  Clear documentation with different scripting language
• 1

  Great ui
• 1

  Inubit Integration
• 1

  Better routing system
• 1

  High performance
• 1

  Runs on Open Telecom Platform
• 1

  Delayed messages
• 1

  Reliability
• 1

  Open-source

Cons of DistributedLog

Cons of Kafka

• 32

  Non-Java clients are second-class citizens
• 29

  Needs Zookeeper
• 9

  Operational difficulties
• 5

  Terrible Packaging

Cons of RabbitMQ

• 9

  Too complicated cluster/HA config and management
• 6

  Needs Erlang runtime. Need ops good with Erlang runtime
• 5

  Configuration must be done first, not by your code
• 4

  Slow