amqp091-go
nsq
| amqp091-go | nsq | |
|---|---|---|
| 2 | 14 | |
| 1,314 | 24,561 | |
| 2.4% | 0.3% | |
| 7.1 | 6.3 | |
| 8 days ago | 7 days ago | |
| Go | Go | |
| GNU General Public License v3.0 or later | 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.
amqp091-go
-
How to plan and execute a large number of tasks in Go?
For rabbitmq I used -> https://github.com/streadway/amqp which is deprecated now for -> https://github.com/rabbitmq/amqp091-go
-
Go and ElasticSearch full-text search microservice in k8s👋✨💫
Elasticsearch client for Go RabbitMQ Go RabbitMQ Client Library Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus Echo web framework Kibana is user interface that lets you visualize your Elasticsearch Docker and docker-compose Kubernetes K8s Helm The package manager for Kubernetes
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?
https://github.com/nsqio/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?
Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
NATS - Golang client for NATS, the cloud native messaging system.
Centrifugo - Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably. Set up once and forever.
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
go-mq - Declare AMQP entities like queues, producers, and consumers in a declarative way. Can be used to work with RabbitMQ.
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Apache Kafka - Mirror of Apache Kafka
machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
sarama - Sarama is a Go library for Apache Kafka. [Moved to: https://github.com/IBM/sarama]
etcd - Distributed reliable key-value store for the most critical data of a distributed system