Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Gearman
Gearman

64
60
+ 1
43
Kafka
Kafka

4.9K
4.4K
+ 1
489
Add tool

Gearman vs Kafka: What are the differences?

Developers describe Gearman as "A generic application framework to farm out work to other machines or processes". Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events. 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.

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

Some of the features offered by Gearman are:

  • Open Source It鈥檚 free! (in both meanings of the word) Gearman has an active open source community that is easy to get involved with if you need help or want to contribute. Worried about licensing? Gearman is BSD
  • Multi-language - There are interfaces for a number of languages, and this list is growing. You also have the option to write heterogeneous applications with clients submitting work in one language and workers performing that work in another
  • Flexible - You are not tied to any specific design pattern. You can quickly put together distributed applications using any model you choose, one of those options being Map/Reduce

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)

"Free" is the primary reason why developers consider Gearman over the competitors, whereas "High-throughput" was stated as the key factor in picking Kafka.

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

Uber Technologies, Spotify, and Slack are some of the popular companies that use Kafka, whereas Gearman is used by Instagram, Hootsuite, and Grooveshark. Kafka has a broader approval, being mentioned in 509 company stacks & 470 developers stacks; compared to Gearman, which is listed in 19 company stacks and 5 developer stacks.

- No public GitHub repository available -

What is Gearman?

Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.

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.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Gearman?
Why do developers choose Kafka?

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

    Be the first to leave a con
    What companies use Gearman?
    What companies use Kafka?

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

    What tools integrate with Gearman?
    What tools integrate with Kafka?

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

    What are some alternatives to Gearman and Kafka?
    RabbitMQ
    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
    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.
    Redis
    Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.
    Beanstalkd
    Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.
    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.
    See all alternatives
    Decisions about Gearman and Kafka
    Roman Bulgakov
    Roman Bulgakov
    Senior Back-End Developer, Software Architect at Chemondis GmbH | 3 upvotes 10.5K views
    Kafka
    Kafka

    I use Kafka because it has almost infinite scaleability in terms of processing events (could be scaled to process hundreds of thousands of events), great monitoring (all sorts of metrics are exposed via JMX).

    Downsides of using Kafka are: - you have to deal with Zookeeper - you have to implement advanced routing yourself (compared to RabbitMQ it has no advanced routing)

    See more
    Kafka
    Kafka
    RabbitMQ
    RabbitMQ

    The question for which Message Queue to use mentioned "availability, distributed, scalability, and monitoring". I don't think that this excludes many options already. I does not sound like you would take advantage of Kafka's strengths (replayability, based on an even sourcing architecture). You could pick one of the AMQP options.

    I would recommend the RabbitMQ message broker, which not only implements the AMQP standard 0.9.1 (it can support 1.x or other protocols as well) but has also several very useful extensions built in. It ticks the boxes you mentioned and on top you will get a very flexible system, that allows you to build the architecture, pick the options and trade-offs that suite your case best.

    For more information about RabbitMQ, please have a look at the linked markdown I assembled. The second half explains many configuration options. It also contains links to managed hosting and to libraries (though it is missing Python's - which should be Puka, I assume).

    See more
    Fr茅d茅ric MARAND
    Fr茅d茅ric MARAND
    Core Developer at OSInet | 2 upvotes 121.8K views
    atOSInetOSInet
    Beanstalkd
    Beanstalkd
    RabbitMQ
    RabbitMQ
    Kafka
    Kafka

    I used Kafka originally because it was mandated as part of the top-level IT requirements at a Fortune 500 client. What I found was that it was orders of magnitude more complex ...and powerful than my daily Beanstalkd , and far more flexible, resilient, and manageable than RabbitMQ.

    So for any case where utmost flexibility and resilience are part of the deal, I would use Kafka again. But due to the complexities involved, for any time where this level of scalability is not required, I would probably just use Beanstalkd for its simplicity.

    I tend to find RabbitMQ to be in an uncomfortable middle place between these two extremities.

    See more
    Interest over time
    Reviews of Gearman and Kafka
    No reviews found
    How developers use Gearman and Kafka
    Avatar of Pinterest
    Pinterest uses KafkaKafka

    http://media.tumblr.com/d319bd2624d20c8a81f77127d3c878d0/tumblr_inline_nanyv6GCKl1s1gqll.png

    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.

    Avatar of opening.io
    opening.io uses GearmanGearman

    Internal, distributed message queue. Main communication happens via port 4730 and consists of simple json messages. Completely independent of the main website back-end.

    Avatar of Coolfront Technologies
    Coolfront Technologies uses KafkaKafka

    Building out real-time streaming server to present data insights to Coolfront Mobile customers and internal sales and marketing teams.

    Avatar of ShareThis
    ShareThis uses KafkaKafka

    We are using Kafka as a message queue to process our widget logs.

    Avatar of Christopher Davison
    Christopher Davison uses KafkaKafka

    Used for communications and triggering jobs across ETL systems

    Avatar of theskyinflames
    theskyinflames uses KafkaKafka

    Used as a integration middleware by messaging interchanging.

    How much does Gearman cost?
    How much does Kafka cost?
    Pricing unavailable
    Pricing unavailable
    News about Gearman
    More news