notify VS simple_gopher

Redis. The pub/sub is sufficient. Here's a notification service that plugs websockets in on one end: https://github.com/go-bridget/notify - I might add in server-side push support, or gobws to keep memory use down. A chat service can be implemented with a rpc API for write operations, and the notify websocket service to deliver events (new messages,...) and state (history, search,...).

I'm a big fan of [Twirp RPC](https://github.com/twitchtv/twirp), and [go-chi/chi](https://github.com/go-chi/chi) if I need to provide REST endpoints, authentication or other routing middleware. The "gorilla" set of packages are also useful, I always reach for gorilla/websocket if I need to do some websocket work. You can look at an example service in [go-bridget/notify](https://github.com/go-bridget/notify) - the main files to look at are under rpc/notify/notify.proto/.go, and the implementation which you write is under server/notify. If you'd create database drivers, I'd create a package under server/notify/mysql (for example), and then implement an interface for data retrieval/settings. It's on the todolist, if I'll ever need to implement anything other than JWT, or Redis. Comment if you have any questions or notes.