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’s 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.
What is Gearman?
What is Kafka?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Gearman?
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
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.
Internal, distributed message queue. Main communication happens via port 4730 and consists of simple json messages. Completely independent of the main website back-end.
Building out real-time streaming server to present data insights to Coolfront Mobile customers and internal sales and marketing teams.