ActiveMQ vs Amazon SQS vs Kafka Manager

ActiveMQ
ActiveMQ

177
200
39
Amazon SQS
Amazon SQS

935
440
125
Kafka Manager
Kafka Manager

36
40
0
- No public GitHub repository available -

What is ActiveMQ?

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

What is Amazon SQS?

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.

What is Kafka Manager?

This interface makes it easier to identify topics which are unevenly distributed across the cluster or have partition leaders unevenly distributed across the cluster. It supports management of multiple clusters, preferred replica election, replica re-assignment, and topic creation. It is also great for getting a quick bird’s eye view of the cluster.

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose ActiveMQ?
Why do developers choose Amazon SQS?
Why do developers choose Kafka Manager?
    Be the first to leave a pro

    Sign up to add, upvote and see more prosMake informed product decisions

    What are the cons of using ActiveMQ?
    What are the cons of using Amazon SQS?
    What are the cons of using Kafka Manager?
      Be the first to leave a con
        Be the first to leave a con
        What companies use ActiveMQ?
        What companies use Amazon SQS?
        What companies use Kafka Manager?

        Sign up to get full access to all the companiesMake informed product decisions

        What tools integrate with ActiveMQ?
        What tools integrate with Amazon SQS?
        What tools integrate with Kafka Manager?

        Sign up to get full access to all the tool integrationsMake informed product decisions

        What are some alternatives to ActiveMQ, Amazon SQS, and Kafka Manager?
        RabbitMQ
        RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
        Kafka
        Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
        Apollo
        Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes.
        Celery
        Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
        ZeroMQ
        The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.
        See all alternatives
        Decisions about ActiveMQ, Amazon SQS, and Kafka Manager
        No stack decisions found
        Interest over time
        Reviews of ActiveMQ, Amazon SQS, and Kafka Manager
        No reviews found
        How developers use ActiveMQ, Amazon SQS, and Kafka Manager
        Avatar of Karma
        Karma uses Amazon SQSAmazon SQS

        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.

        Avatar of Brandon Adams
        Brandon Adams uses Amazon SQSAmazon SQS

        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.

        Avatar of Simple Merchant
        Simple Merchant uses Amazon SQSAmazon SQS

        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.

        Avatar of Casey Smith
        Casey Smith uses ActiveMQActiveMQ

        Remote broker and local client for incoming data feeds. Local broker for republishing data feeds to other systems.

        Avatar of Olo
        Olo uses Amazon SQSAmazon SQS

        Primary message queue. Enqueueing operations revert to a local file-system-based queue when SQS is unavailable.

        Avatar of IndiTip
        IndiTip uses Amazon SQSAmazon SQS

        I can't afford to lose data if Dynamo throttles my writes, so everything goes into a message queue first.

        How much does ActiveMQ cost?
        How much does Amazon SQS cost?
        How much does Kafka Manager cost?
        Pricing unavailable
        Pricing unavailable
        News about ActiveMQ
        More news
        News about Kafka Manager
        More news