groupcache VS ngrok

As shown in the title, DREAMEMO is a distributed cache with out-of-the-box, high-scalability, modular-design features.The groupcache implementation is referenced, and re-structured, specific module differentiation is as follows:

I remember one of the first real-world uses of Go being the groupcache package: https://github.com/golang/groupcache (to serve Chrome downloads, IIRC?)

> comes with a cache filling mechanism. Whereas memcached just says "Sorry, cache miss", often resulting in a thundering herd of database (or whatever) loads from an unbounded number of clients (which has resulted in several fun outages), groupcache coordinates cache fills such that only one load in one process of an entire replicated set of processes populates the cache, then multiplexes the loaded value to all callers.

I read that group cache (https://github.com/golang/groupcache) can be used to sync servers around a key.

I've not tried this myself, but I've seen it suggested to use groupcache (https://github.com/golang/groupcache) to sync your servers.

https://github.com/golang/groupcache is managing distributed caching that addresses thundering herd problem of memcache.

How it goes sometimes. Check out https://github.com/golang/groupcache and of course the AWS golang SDK.

There is also groupcache, written by the same author as memcached, but better.

Thanks for the history. I maintain this list[0], and wasn't aware of OG localtunnel, likely because there's a somewhat newer and now more popular project with the same name[1]. You appear to be correct on timing. Here's the earliest commits on GitHub for each of the projects:

OG localtunnel (2010): https://github.com/progrium/localtunnel/tree/fb82920d9d3e538...

Other localtunnel (2012): https://github.com/localtunnel/localtunnel/tree/93d62b9dbb9f...

ngrok (2012): https://github.com/inconshreveable/ngrok/tree/8f4795ecac7f92...

I'll see that OG localtunnel gets added to the list for posterity.

[0]: https://github.com/anderspitman/awesome-tunneling

[1]: https://github.com/localtunnel/localtunnel

ngrok

if you're worried about the line "ngrok captures and analyzes all traffic over the tunnel for later inspection and replay" in https://github.com/inconshreveable/ngrok, I'd say that's a valid concern but not for ssh if you make sure the client knows what the host key is and does not accept a different one

Looks like it's open source so it could be just a fork away https://github.com/inconshreveable/ngrok

To get a fix domain, we can deploy HTTP tunnel in our own server. ngrok also provides an open source version for server side deployment. But it is old 1.x version and not recommended to deploy at production with some serious reliability issues.

I ended up inspired by ngork structure here: https://github.com/inconshreveable/ngrok it doesn't really work well with go modules, since i will end up running project like this:

Maybe https://github.com/inconshreveable/ngrok/issues/408

In Go, inconshreveable/ngrok and coyove/goflyway is well known, especially ngrok is popular among developers as a SaaS service.

> > DO NOT RUN THIS VERSION OF NGROK (1.X) IN PRODUCTION

> I don't see that anywhere.

I didn't find it on the website, but I did find it on the GitHub:

https://github.com/inconshreveable/ngrok