go-proxy-cache
nsq
Our great sponsors
| go-proxy-cache | nsq | |
|---|---|---|
| - | 14 | |
| 117 | 24,561 | |
| - | 0.6% | |
| 4.8 | 6.3 | |
| 6 days ago | 5 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.
go-proxy-cache
We haven't tracked posts mentioning go-proxy-cache yet.
Tracking mentions began in Dec 2020.
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?
lfu-redis - LFU Redis implements LFU Cache algorithm using Redis as data storage
NATS - Golang client for NATS, the cloud native messaging system.
simple-jwt-provider
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
Ponzu - Headless CMS with automatic JSON API. Featuring auto-HTTPS from Let's Encrypt, HTTP/2 Server Push, and flexible server framework written in Go.
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
psql-streamer - Stream database events from PostgreSQL to Kafka
Apache Kafka - Mirror of Apache Kafka
goproxy - π¦ goproxy is a proxy server which can forward http or https requests to remote servers./ goproxy ζ―δΈδΈͺεε代ηζε‘ε¨οΌζ―ζ转ε http/https θ―·ζ±γ
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
etcd - Distributed reliable key-value store for the most critical data of a distributed system