nsq
docker-compose
Our great sponsors
| nsq | docker-compose | |
|---|---|---|
| 14 | 3 | |
| 24,530 | 251 | |
| 0.5% | 6.8% | |
| 6.3 | 7.1 | |
| 1 day ago | 18 days ago | |
| Go | Shell | |
| MIT License | 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.
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
docker-compose
-
Temporal
I'm very intrigued and excited to give it a try (literally just ran docker compose up repo and its taking a while to build, probably because I have terrible internet here in the boonies). Curious if anyone here has used it yet, and if so, what you thought about it.
-
Measuring Developer Relations
Examples: Netlify has an entire Integrations Engineering team. Currently it just works on Next.js integrations, but it could also own, for example, the VS Code extension. In the past I helped build out Netlify Dev and react-netlify-identity as part of this function. Popular quick start tooling like Docker Compose and Helm Charts also fall under this function.
- For those running Go in production at scale, what do you use for distributed task queues?
What are some alternatives?
NATS - Golang client for NATS, the cloud native messaging system.
helm-charts - Temporal Helm charts
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
cadence - Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
temporal - Temporal service
Apache Kafka - Mirror of Apache Kafka
Asynq - Simple, reliable, and efficient distributed task queue in Go
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
orbit-model - A framework for building high gravity communities 🪐
etcd - Distributed reliable key-value store for the most critical data of a distributed system
gq - gq is a lightweight scalable message queue backed by the most popular SQL DBs. Add message queue semantics to your application without integrating extra infrastructure.