jw989

I agree with this. Other than this it's a great project, nice work!

Well, you're main app should obviously not be clustered but think about the api you use to manage data. I don't know your architecture but I'm sure that you can separate your api from your user state and cluster those apis as well as use various reverse proxies and load balancing services.

Wow this is very close to what I was saying. Thanks for this

This is cool, largely because of the functional perspective to dealing with pools of websockets. I personally think the next level for websockets infrastructure is building a paradigm for large pools of concurrent websocket connections.

Perhaps a microservces implementation with each step (handshake, broadcasting, http overhead) having their own cluster and communicating through channels.

I really enjoyed reading this.

However, I personally feel distain for the perspective of how every engineer should maintain a noble sense of worth. No matter the environmental differences of being in SF or elsewhere, people are bad at engineering wall to wall. While there are still successes at both sides of the coin.

Frankly, 'Software eating the world' has nothing to do with us. It has to do with, well, the world. And my own struggle with the tech industry is how disconnected we are in the 'startup and grow' sector.

The main problem I have with Jet.com is that never have I or anyone I know (limited in breadth but still) thought "well, Amazon isn't providing me with what I need so I'll go to jet.com for this"

If anyone has had an experience like this I would love to hear it.

From my understanding golang is a perfectly fine name for Go and much easier to Google.