WebSocket alternative

WebRTC vs WebSockets – Key Differences WebRTC is more secure ; At the moment, WebRTC is only supported by certain browsers while WebSockets is compatible with almost all existing browsers; In terms of scalability, WebSockets uses a server per session approach and WebRTC is peer-to-peer.

HTTP/2 is not a replacement for push technologies such as WebSocket or SSE . HTTP/2 Push server can only be processed by browsers, not by applications. Combining HTTP/2 and SSE provides efficient HTTP-based bidirectional communication.

As of today, using WebSockets is a viable option, but because of how new it is, the road may still be a little bumpy . As the use of the technology spreads it should become easier to implement, which will continue to increase its use.

Websockets are largely obsolete because nowadays, if you create a HTTP/2 fetch request, any existing keepalive connection to that server is used, so the overhead that pre-HTTP/2 XHR connections needed is lost and with it the advantage of Websockets.