CODEWITHSUNDEEP
websocketgo
jiorry
jiorry

Reputation: 31

What's the best way to store websocket connection in golang

I wrote a web chat app, using websockets. It uses one connection per page to push new messages to online users.

So, there are a lot of websocket.Conn to manage. I'm currently using a map.

onlineUser = map[int] *websocket.Conn

I am very worried about the map when 1,000,000 pages are open.

There is a better way to store all the websocket.Conn?

Erlang's inner database can be used to store an erlang socket.

For Go, I had considered using "encoding/gob" to cache the socket in memcached or redis. But then before using the websocket.Conn it but be GOB decoded and that will consume too much CPU.

Upvotes: 0

Views: 4105

Answers (1)

deft_code
deft_code

Reputation: 59347

1,000,000 concurrent users is a nice problem to have. :)

Your primary problem is that the websocket spec requires the connection to be maintained open. This means that you can't serialize and cache them.

However, if you could GOB encode them, and every user sent one message a second (unrealistically high IMO) a million GOB decodes per second isn't going to dominate your load.

Also a map can easily handle a million entries.

If you really want to worry about future scaling, figure out how to get two instances of your application to work together on the load. Then increase that to N instances.

Upvotes: 3

Related Questions