WEBRTC ARCHITECTURE

 THERE ARE THREE TYPES OF ARCHITECTURES,

1. P2P

2. SFU

3. MCU

EACH SYSTEM IS CALLED AS NODE.

1. P2P ( PEER TO PEER) : 

IT IS A SERVERLESS ARCHITECTURE.

EACH SYSTEM CAN DIRECTLY COMMUNICATE AND SHARE DATA WITH EACH OTHER.

IT IS WELL SUITED FOR LESS NUMBER OF NODES.

GENERALLY, EACH SYSTEM (NODE) HAS SOME PARTICULAR BANDWIDTH LIMIT UPTO WHICH IT CAN ACCEPT DATA. 

WHEN THERE ARE MORE NUMBER OF NODES THE LOAD ON THE NODES INCREASES AND EVENTUALLY IT CRASHES.

IN P2P, AS EACH SYSTEM (NODE) CAN DIRECTLY SEND OR RECEIVE DATA THE BANDWIDTH AND RESOURCE CONSUMPTION IS HIGH.

WEBRTC WAS BUILT ON P2P.


SFU:

SELECTIVE FORWARDING UNIT.



FOR NODE A , IT SENDS STREAM OF DATA TO THE SERVER AND RECEIVES THE STREAM FROM SERVER. HERE, DATA IS SENT TO THE SERVER, RECEIVES THE DATA OF OTHER NODES (B,C AND D) FROM THE SERVER.

THE STREAM IS UPLOADED ONLY ONCE , AND DOWNLOADED MULTIPLE TIMES.

IN P2P, NODE A HAS TO SEND IT'S STREAM THRICE i.e TO NODES B,C AND D.

BUT HERE, IT HAS TO SEND IT'S STREAM ONLY ONCE i.e TO THE SERVER. 

IN P2P, WHEN A PARICULAR NODE REACHES IT'S BANDWIDTH LIMIT , THE DATA FROM OTHER NODES CANNOT BE RECEIVED BY THAT NODE.

BUT , IN SFU WHEN THE SERVER DETECTS THAT A PARTICULAR NODE REACHES IT'S LIMIT IT STARTS TO SEND LESS DATA PACKETS i.e LOW QUALITY OR IT WOULD STOP SENDING VIDEO FILES AND WOULD ONLY SEND AUDIO FILES.


MCU: 

MULTI POINT CONTROL UNIT.


IN THIS TYPE OF ARCHITECTURE , SERVER BEARS A LOT OF LOAD, BECAUSE ALL THE NODES NEEDS TO UPLOAD AND DOWNLOAD ONLY ONCE.

IN THE MCU ARCHITECTURE , THE SERVER COMBINES ALL THE SERVERS THAT NODES SEND TO IT AND GIVES A SINGLE STREAM TO EACH NODE.

THIS TYPE OF ARCHITECTURE IS USED IN WEBINARS.

                   UPLOAD        DOWNLOAD

P2P                  N                          N

SFU                 1                           N

MCU               1                           1







Comments

Popular posts from this blog

MIDDLEWARE.JS

MODELS

AUTHENTICATION PAGE