Kafka vs MSMQ: What are the differences?
Kafka: 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; MSMQ: A technology for asynchronous messaging. This technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. Applications send messages to queues and read messages from queues.
Kafka and MSMQ can be primarily classified as "Message Queue" tools.
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.
What is Kafka?
What is MSMQ?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose MSMQ?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using MSMQ?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with MSMQ?
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.
Building out real-time streaming server to present data insights to Coolfront Mobile customers and internal sales and marketing teams.