Re:Heroku WebSockets Now in Public Beta
by nivertech on Tuesday October 08, 2013 @02:15PM
(#6516765)
How did you solved ELB 60s disconnections for idle Websocket connections?
I know it can be increased, but not by too much.
EDIT: also when 2 years ago I did load testing with ELB and created 1 million concurrent WebSocket connections, I did received mail from Amazon asking what the hell I doing and was asked to stop it ;)
The ELB idle connection rule still applies: https://devcenter.heroku.com/articles/heroku-labs-websockets...
You'll need to send some data every ~55s or so in order to keep the connection alive.
This idle timeout can be increased by at least an order of magnitude now, upon request to AWS. Open a ticket.
> As the WebSocket standard is very recent, it has never been supported by ELBs in HTTP mode.
WebSocket has been around since 2010. This is just confirmation to me that Heroku isn't a good fit for apps targeting new web technologies. It's a good fit for apps targeting IE8.
Re:Heroku WebSockets Now in Public Beta
by mwmanning on Tuesday October 08, 2013 @04:34PM
(#6517654)
By that logic AWS isn't a good fit for new web technologies either, since that was the blocker here.
This is why I would never use any PaaS, only IaaS. IaaS providers don't do blog posts proudly declaring that they now support 3 year old technology.
> IaaS providers don't do blog posts proudly declaring that they now support 3 year old technology.
http://aws.typepad.com/aws/2013/07/elastic-load-balancing-ad...
Re:Heroku WebSockets Now in Public Beta
by neilmiddleton on Tuesday October 08, 2013 @06:07PM
(#6518150)
AWS is an IaaS ??
ELB is their PaaS offering.
Re:Heroku WebSockets Now in Public Beta
by acjohnson55 on Tuesday October 08, 2013 @07:08PM
(#6518465)
I think you're thinking of Elastic Beanstalk
As the WebSocket standard is very recent, it has never been supported by ELBs in HTTP mode.
ELBs in TCP mode can support any TCP traffic. It's become clear that we need this flexibility, so we're moving to TCP-mode ELBs now. This was not trivial, though, as long-lived connections (like those used for WebSockets) have different implications for our HTTP routers. That had to be taken account.
Nonetheless, we've had a private beta for a long time that worked as described above. But we deemed it insufficient for general customer use because TCP-mode ELBs mean that you lose the client's source IP and protocol. Fortunately, ELBs now have Proxy Protocol support [2], which allows us to keep that request information that Heroku apps typically rely on.
[1] More info on ELB modes: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Devel...
[2] http://aws.typepad.com/aws/2013/07/elastic-load-balancing-ad...