Amazon SQS vs DoctorKafka: What are the differences?
Developers describe Amazon SQS as "Fully managed message queuing service". Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use. On the other hand, DoctorKafka is detailed as "A service for Kafka cluster auto healing and workload balancing". DoctorKafka can automatically detect broker failure and reassign the workload on the failed nodes to other nodes. DoctorKafka can also perform load balancing based on topic partitions's network usage, and makes sure that broker network usage does not exceed the defined settings.
Amazon SQS and DoctorKafka can be primarily classified as "Message Queue" tools.
DoctorKafka is an open source tool with 488 GitHub stars and 68 GitHub forks. Here's a link to DoctorKafka's open source repository on GitHub.
What is Amazon SQS?
What is DoctorKafka?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose DoctorKafka?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using DoctorKafka?
What companies use DoctorKafka?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
In the beginning we thought we wanted to start using something like RabbitMQ or maybe Kafka or maybe ActiveMQ. Back then we only had a few developers and no ops people. That has changed now, but we didn't really look forward to setting up a queuing cluster and making sure that all works.
What we did instead was we looked at what services Amazon offers to see if we can use those to build our own messaging system within those services. That's basically what we did. We wrote some clients in Ruby that can basically do the entire orchestration for us, and we run all our messaging on both SNS and SQS. Basically what you can do in Amazon services is you can use Amazon Simple Notification Service, so SNS, for creating topics and you can use queues to subscribe to these topics. That's basically all you need for a messaging system. You don't have to worry about scalability at all. That's what really appealed to us.
This isn't exactly low-latency (10s to 100s of milliseconds), but it has good throughput and a simple API. There is good reliability, and there is no configuration necessary to get up and running. A hosted queue is important when trying to move fast.
SQS is the bridge between our new Lambda services and our incumbent Rails applications. Extremely easy to use when you're already using other AWS infrastructure.
Primary message queue. Enqueueing operations revert to a local file-system-based queue when SQS is unavailable.