Stacks29

Followers29

Votes34

Kafka

Stacks3.2K

Followers2.5K

Votes459

Kafka Manager

Stacks36

Followers40

Votes0

- No public GitHub repository available -

What is IronMQ?

An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.

What is Kafka?

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

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 IronMQ?

Why do developers choose Kafka?

Why do developers choose Kafka Manager?

11
Great Support
7
Heroku Add-on
3
Delayed delivery upto 7 days
3
Push support
2
Good analytics/monitoring
2
Ease of configuration
2
Language agnostic

96
High-throughput
93
Distributed
75
Scalable
67
High-Performance
59
Durable
29
Publish-Subscribe
16
Simple-to-use

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 IronMQ?

What are the cons of using Kafka?

What are the cons of using Kafka Manager?

1
Can't use rabbitmqadmin

12
Needs Zookeeper
10
Non-Java clients are second-class citizens
2
Operational difficulties

Be the first to leave a con

What companies use IronMQ?

What companies use Kafka?

What companies use Kafka Manager?

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

What tools integrate with IronMQ?

What tools integrate with Kafka?

What tools integrate with Kafka Manager?

Kafka

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

What are some alternatives to IronMQ, Kafka, 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.

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.

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.

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.

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 IronMQ, Kafka, and Kafka Manager

No stack decisions found

Related Comparisons

Interest over time

Reviews of IronMQ, Kafka, and Kafka Manager

Umur Ozkul

Co-Founder at Publitory

Review of

IronMQ

I deploy to Heroku. However, my applications require full linux applications that cannot be deployed to Heroku. I deploy them to Rackspace.

Then Heroku and Rackspace communicate over IronMQ. Problem solved.

How developers use IronMQ, Kafka, and Kafka Manager

Pinterest uses

Kafka

Front-end messages are logged to Kafka by our API and application servers. We have batch processing (on the middle-left) and real-time processing (on the middle-right) pipelines to process the experiment data. For batch processing, after daily raw log get to s3, we start our nightly experiment workflow to figure out experiment users groups and experiment metrics. We use our in-house workflow management system Pinball to manage the dependencies of all these MapReduce jobs.