Deep Licode Architecture and understanding

[cracker0dks]

Hey,
since there is no complete model and description of the licode architecture, I tried to understand it by the simple model on the licode docu and reading in the licode google group. Here is my approach:

Short Informations I found all around the components:

• Nuve Manage Erizo Controllers (can create more than one Erizo Controller if needed for scale)
• MongoDB: Stores room and users in rooms
• Erizo Controler: Manage rooms and the users in it
• MCU - Erizo Agent: The C++ MCU that broadcast video/audio
• RabbitMQ: handles the propagation of media elements. It creates the media pipeline.

Is this correct and can you please add Information if you know ?
You can edit the model if you want at: https://docs.google.com/drawings/d/1KIRmaJHh2GUH3rDQWXrnwhwhtI5FAdnBOFAptlvIo2s/edit

You can also add this or something like this to the doc on the licode page for better understanding?

[zevarito]

Great initiative!

2015-07-30 17:15 GMT-03:00 cracker0dks notifications@github.com:

Hey,
since there is no complete model and description of the licode
architecture, I tried to understand it by the simple model on the licode
docu and reading in the licode google group. Here is my approach:

[image: licode architecture 1]
https://cloud.githubusercontent.com/assets/1816621/8993885/26fdff9c-3708-11e5-9f57-3554754079dd.png

Short Informations I found all around the components:

• Nuve Manage Erizo Controllers (can create more than one Erizo
  Controller if needed for scale)
• MongoDB: Stores room and users in rooms
• Erizo Controler: Manage rooms and the users in it
• MCU - Erizo Agent: The C++ MCU that broadcast video/audio
• RabbitMQ: handles the propagation of media elements. It creates
  the media pipeline.

Is this correct and can you please and Information if you know ?
You can edit the model if you want at:
https://docs.google.com/drawings/d/1KIRmaJHh2GUH3rDQWXrnwhwhtI5FAdnBOFAptlvIo2s/edit

You can also add this or something like this to the doc on the licode page
for better understanding?

—
Reply to this email directly or view it on GitHub
#335.

Alvaro

[lodoyun]

Actually, it's more like this:

• Nuve Manages Services (Custom APPs), Rooms and Users, generates tokens for delegated auth so custom apps can provide access to users. It balances the Rooms among the available ErizoControllers.
• MongoDB Only used by Nuve to store information about rooms and tokens. No user information is managed by Licode.
• Erizo Controler Manages Control, signalling and data streams for the rooms assigned to it by Nuve. New started ErizoControllers are automatically discovered by Nuve as long as they are connected to the same RabbitMQ instance.
• MCU - Erizo Agent+ErizoJS (ErizoAPI+ErizoC++): Distributed MCU. A better explanation on how this works is available here ErizoJS is NOT erizo.js from the client side, sorry about the naming confusion.
• RabbitMQ: Message broker, enables the distribution of the architecture. Handles all the messages among the components of Licode. It does not handle media and/or communicate with the Clients.

[cracker0dks]

Wow! Thank you very much for the awesome explanation!

[guogenfang]

Great,very helpful