KafkaHQ VS NSQ

KafkaHQ Reviews

NSQ Reviews

KafkaHQ mentions (3)

• Show HN: After AKHQ (KafkaHQ), I Made Kestra Open-Source Airflow Alternative

  The project start as a side project (yet another side project I do the night and weekend) but was quickly promoted and used in a French Big Retail Company. This one trust on the project and decide to go production with Kestra. So they decide to inject some resource in order to develop some features that need and that is missing. But basically, not so much people for now. We are trying to start a community around... - Source: Hacker News / about 2 years ago

• Show HN: After AKHQ (KafkaHQ), I Made Kestra Open-Source Airflow Alternative

  Hey HN, I'm really proud to share with you my new open source project: Kestra https://github.com/kestra-io/kestra I created a few years ago a successful open source AKHQ project: https://github.com/tchiotludo/akhq (renamed from KafkaHQ) which has been adopted by big companies like Best Buy, Pipedrive, BMW, Decathlon and many more. 2300 stars, 120 contributors, 10M docker downloads, much more than I expected. Now... - Source: Hacker News / about 2 years ago

• Kestra, infinitely scalable open source orchestration and scheduling platform.

  Three years ago, I started another open source project, AKHQ, with the same license. Working with a successful project was an invaluable experience for me as I was able to learn how to build a community around a project. I've also learnt that an open source system won't pay the bills on its own. AKHQ required a lot of personal investment; Kestra has required a lot more and will continue to do so in the future!... - Source: dev.to / about 2 years ago

NSQ mentions (7)

• Any thoughts on using Redis to extend Go's channels across application / machine boundaries?

  (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

• FileWave: Why we moved from ZeroMQ to NATS

  Bit.ly's NSQ is also an excellent message queue option. Source: about 1 year ago

• Infinite loop pattern to poll for a queue in a REST server app

  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

• What are pros and cons of Go?

  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

• Distributed IM Service in Golang

  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