Chronicle Queue
nsq
Our great sponsors
| Chronicle Queue | nsq | |
|---|---|---|
| 2 | 14 | |
| 3,152 | 24,530 | |
| 1.0% | 0.5% | |
| 9.3 | 6.3 | |
| about 14 hours ago | 1 day ago | |
| Java | Go | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Chronicle Queue
-
Cues: low-latency persistent blocking queues, processors, and graphs via ChronicleQueue
Cues extends ChronicleQueue and Tape to provide:
- Micro second messaging that stores everything to disk
nsq
- NSQ: Open-source realtime distributed messaging, billions of messages / day
-
MQTT vs. Kafka: An IoT Advocate's Perspective
Interesting. What are you thoughts on NSQ?
Was looking at it earlier today, but haven't ever tried it out.
-
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.
-
FileWave: Why we moved from ZeroMQ to NATS
Bit.ly's NSQ is also an excellent message queue option.
-
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.
- NSQ – A realtime distributed messaging platform
-
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)
- Nsq - A realtime distributed messaging platform
- Is there any conventionally accepted repo that is representative of well designed go code ?
- NSQ: A realtime distributed messaging platform
What are some alternatives?
Apache Kafka - Mirror of Apache Kafka
NATS - Golang client for NATS, the cloud native messaging system.
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Agrona - High Performance data structures and utility methods for Java
Apache ActiveMQ - Mirror of Apache ActiveMQ
Redisson - Redisson - Easy Redis Java client with features of In-Memory Data Grid. Sync/Async/RxJava/Reactive API. Over 50 Redis based Java objects and services: Set, Multimap, SortedSet, Map, List, Queue, Deque, Semaphore, Lock, AtomicLong, Map Reduce, Bloom filter, Spring Cache, Tomcat, Scheduler, JCache API, Hibernate, RPC, local cache ...
etcd - Distributed reliable key-value store for the most critical data of a distributed system