Go HTTP server provides great scalability, allocating a goroutine per connection, and reusing the efficient multiplexing and scheduling of the Go runtime. While this technique is almost ideal for most scenarios, it comes with limited scale for websockets applications due to high memory consumption In this talk, we will show how we’ve implemented our own event loop mechanism to overcome those limit
![Going Infinite, handling 1M websockets connections in Go](https://cdn-ak-scissors.b.st-hatena.com/image/square/6628601f78e344a582e0907583fa424419a66e2b/height=288;version=1;width=512/https%3A%2F%2Ffiles.speakerdeck.com%2Fpresentations%2F901175eedc334d18aa6e1d6b0b28d0f3%2Fslide_0.jpg%3F11772315)