Kafka vs LogDevice: 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; LogDevice: Log storage for high-durability low-latency streaming use cases (by Facebook). LogDevice is a scalable and fault tolerant distributed log system. While a file-system stores and serves data organized as files, a log system stores and delivers data organized as logs. The log can be viewed as a record-oriented, append-only, and trimmable file.
Kafka belongs to "Message Queue" category of the tech stack, while LogDevice can be primarily classified under "Logging Tools".
Kafka and LogDevice are both open source tools. Kafka with 12.7K GitHub stars and 6.81K forks on GitHub appears to be more popular than LogDevice with 1.52K GitHub stars and 136 GitHub forks.
What is Kafka?
What is LogDevice?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose LogDevice?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using LogDevice?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with LogDevice?
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.