REST vs WebSocket Comparison and Benchmarks - Miles to go 2.0 ...

REST vs WebSocket Comparison and Benchmarks - Miles to go 2.0 ...

WebSocket is a low-level protocol, think of it as a socket on the web. Every thing, including a simple request/response design pattern, how to create/update/delete resources need, status codes etc to be build on top of it. All of these are well defined for HTTP.

WebSocket is a stateful protocol where as HTTP is a stateless protocol. WebSocket connections are know to scale vertically on a single server where as HTTP can scale horizontally. There are some proprietary solutions for WebSocket horizontal scaling, but they are not standards-based.

HTTP comes with a lot of other goodies such as caching, routing, multiplexing, gzipping and lot more. All of these need to be defined on top of WebSocket.

How will Search Engine Optimization (SEO) work with WebSocket ? Works very well for HTTP URLs.

All proxy, DNS, firewalls are not yet fully aware of WebSocket traffic. They allow port 80 but might restrict traffic by snooping on it first.

Security with WebSocket is all-or-nothing approach.

Read full article from REST vs WebSocket Comparison and Benchmarks - Miles to go 2.0 ...