nsq VS exposure-notifications-server

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.

(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.

Bit.ly's NSQ is also an excellent message queue option.

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.

distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on)

Not a small one, but a real-life one, the exposure-notifications-server is usually what I like to recommend, keep in mind that you probably need a bit of Go knowledge and context before looking at it so perhaps it isn't the best introductory project to look at; however I recommend you to bookmark it for future reference.

Here, I can even link you to an article of how exposure notifications work: https://www.google.com/covid19/exposurenotifications/

Google's Exposure Notification Reference Serve is a real life example of what you're asking for.

Which is just a massive misunderstanding of how the contact tracing API works, even if you do believe that it was "surreptitiously installed ... on users [sic] phones".

https://www.google.com/covid19/exposurenotifications/ (“The Exposure Notifications System was introduced in an update to Google Play Services. This update did not automatically turn on Exposure Notifications or enable any Exposure Notifications functionality. Exposure Notifications only works if you decide to opt-in.”) Android 6.0 and above.

Source: https://www.google.com/covid19/exposurenotifications/