rdkafka might be a bit more popular than NSQ. We know about 7 links to it since March 2021 and only 7 links to NSQ. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
(G)NATS can do millions of messages per second and is the right tool for the job (either that or NSQ). Redis isn't even the fastest Redis protocol implementation, KeyDB significantly outperforms it. Source: about 1 year ago
Bit.ly's NSQ is also an excellent message queue option. Source: about 1 year ago
Queue consumers are interesting because there are many solutions for them, from using Redis and persisting the data in a data store - but for fast and scalable the approach I would take is something like SQS (as I advocate AWS even free tier) or NSQ for managing your own distributed producers and consumers. Source: over 1 year ago
Distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on). Source: almost 2 years ago
NSQ is a message queue implemented by Golang, and all messages are routed through NSQ. Reasons for choosing NSQ compared to other MQs: decentralized distribution (direct connection between production and consumption), low latency, No ordering, high performance, simple binary protocol. - Source: dev.to / about 2 years ago
We could have made some changes at the librdkafka level (see this), but we didn’t really want to pursue this (at least not yet). - Source: dev.to / over 1 year ago
As my first "real world" (ish) project in Vlang, I'm trying to copy https://github.com/confluentinc/confluent-kafka-go, which is a Go wrapper for Kafka C client library, https://github.com/edenhill/librdkafka. Source: over 1 year ago
If you're using Kafka in a Node.js app, it's likely that you'll need node-rdkafka. This is a library that wraps the librdkafka library and makes it available in Node.js. According to the project's README, "All the complexity of balancing writes across partitions and managing (possibly ever-changing) brokers should be encapsulated in the library.". - Source: dev.to / over 1 year ago
You are right, but in practice that's not what happens. Companies do not rely on open source libraries, the developers working for such companies do. I can give you a realistic example. If you want to use Kafka and Go, your probably only option is to use https://github.com/confluentinc/confluent-kafka-go. Its LICENSE explicitly says "no warranty". Now, what if I find a bug in the library? Only two realistic... - Source: Hacker News / over 1 year ago
Librdkafka – An Apache Kafka C/C++ client library\ (9 comments). Source: about 2 years ago
ZeroMQ - ZeroMQ is a high-performance asynchronous messaging library.
Kafka Manager - A tool for managing Apache Kafka.
RabbitMQ - RabbitMQ is an open source message broker software.
KafkaCenter - See what developers are saying about how they use KafkaCenter. Check out popular companies that use KafkaCenter and some tools that integrate with KafkaCenter.
nanomsg - nanomsg is a socket library that provides several common communication patterns.
KafkaHQ - Kafka GUI for Apache Kafka to manage topics, topics data, consumers group, schema registry, connect and more... - tchiotludo/kafkahq