When considering millions of connections spread across many servers, short-lived https connections are much easier to load balance and plan for than long-lived websockets. Websockets certainly have their advantages, but in this case https is much more appropriate, and also easier for 3rd party developers to pick up and use.
You are viewing a single comment's thread from:
httpsconnections are exactly the same aswssconnections, except they're "upgraded"httpsconnections. Also, the fact they are now usingkeep-alivewould negate your point that they're extracting some benefit by using "short-lived https connections".Except, they do not scale well. Go try to load balance millions of websocket connections and see how that goes :)
Exactly.
We have difficulties with performance already. This approach will only worsen the situation.