Apache ActiveMQ VS NSQ

Apache ActiveMQ Reviews

NSQ Reviews

Apache ActiveMQ mentions (5)

• Top 6 message queues for distributed architectures

  Apache ActiveMQ is an open-source Java-based message queue that can be accessed by clients written in Javascript, C, C++, Python and .NET. There are two versions of ActiveMQ, the existing “classic” version and the next generation “Artemis” version, which is currently being worked on. - Source: dev.to / 11 months ago

• Data Engineering and DataOps: A Beginner's Guide to Building Data Solutions and Solving Real-World Challenges

  For real-time streaming, we have other frameworks and tools like Apache Kafka, ActiveMQ, and AWS Kinesis. - Source: dev.to / over 1 year ago

• Interview for JetBrains: Why Localazy developers ️ Kotlin?

  The back-end is designed as a set of microservices communicating through a message broker, ActiveMQ, with a custom configuration to support delayed delivery and other features. - Source: dev.to / almost 2 years ago

• Advice for real-time UDP over the internet

  My suggestion would be: don't try to reinvent the wheel. There are communications solutions out there already intended for this kind of use case, like https://activemq.apache.org/ (I point this out because Amazon MQ is based on ActiveMQ). Source: almost 2 years ago

• Sending message asynchronously (JSM)

  First we have to run a broker in my case I use activeMq You can download the file zip and after extract the file you can acces to the bin foler and run. - 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