Why is WebRTC so complex?

WebRTC (Web Real-Time Communication) is a collection of communications protocols and application programming interfaces that enable real-time communication over peer-to-peer connections .

There a number of protocols that will be used at the application layer for WebRTC : HTTP – Hypertext Transfer Protocol. WebSocket – JavaScript interface, SRTP – Secure Real-time Transport Protocol.

For Web developers, the most important part is WebRTC API. … In this model, both devices are running a web application from different servers. The RTCPeerConnection object configures streams so they could connect to each other, peer-to-peer. This signaling is done via HTTP or WebSockets.

The future is the IoT, and WebRTC is developing the necessary framework for continued innovation : free, high-quality technology that enables P2P connections—connections that work regardless of device, provider, or preferred web browser.

WebRTC (Web Real-Time Communication) is a free and open-source project providing web browsers and mobile applications with real-time communication (RTC) via application programming interfaces (APIs) .

WebRTC is an over-engineered Rube Goldberg machine for many reasons, including the fact that it tries to include so many capabilities in a single standard. It’s also complex because STUN, TURN, and ICE are overly complex . WebRTC should have used a simpler underlying design. You really, really don’t need all that.

The stack is data channel only , it does not do audio/video which is useful for many types of usages. … For example communication between different versions of a game with some players are using native code and some using web applications. We use it for secure and scalable remote desktop and file transfers.