BigBlueButton is built upon a solid foundation of underlying components, including NGINX, FreeSWITCH, Kurento, Redis, Node.js, React.js, and others.
This page describes the overall architecture of BigBlueButton and how these components work together.
The following diagram provides a high-level view of how BigBlueButton's components work together.
We'll break down each component in more detail below.
The HTML5 client is a single page, responsive web application that is built upon the following components:
- React.js for rendering the user interface in an efficient manner
- WebRTC for sending/receiving audio and video
The HTML5 client connects directly with the BigBlueButton server over port 443 (SSL), from loading the BigBlueButton client to making a web socket connection. These connections are all handled by nginx.
The HTML5 server sits behind nginx.
The HTML5 server is built upon
- Meteor.js in ECMA2015 for communication between client and server.
- MongoDB for keeping the state of each BigBlueButton client consistent with the BigBlueButton server
The MongoDB database contains information about all meetings on the server and, in turn, each client connected to a meeting. Each user's client is only aware of the their meeting's state, such the user's public and private chat messages sent and received. The client side subscribes to the published collections on the server side. Updates to MongoDB on the server side are automatically pushed to MiniMongo on the client side.
The following diagram gives an overview of the architecture of the HTML5 client and its communications with the other components in BigBlueButton.
Scalability of HTML5 server component
BigBlueButton 2.2 used a single
nodejs process for all client-side communication. This process would start to bottleneck (the
nodejs process, running on a single CPU core, started to use 100% of the core). Because
nodejs was running on a single CPU core, having a 16 or 32 CPU core server for BigBlueButton 2.2 failed to yield much additional scalability.
BigBlueButton 2.3 moves away from a single
nodejs process for
bbb-html5 towards multiple
nodejs processes handling incoming messages from clients. This means that
bbb-html5 could use multiple CPU cores for processing messages and handling browser sessions (each
nodejs process runs on a single CPU core).
As of 2.3-alpha-7,
bbb-html5 uses 2 "frontend" and two "backend" processes (this value is configurable in
bbb-html5-with-roles.conf, see Configuration Files). A restart of BigBlueButton is required if you make changes to these files.
The breakdown of functionality between front-end and back-end is as follows
- receive the
ValidateAuthTokenRespevent to complete authentication
- collection subscription and publishing
- other DDP events including method calls to send events to
- handle completely the Streamer redis events: Cursor, Annotations, External video share
- still require
MeetingEndedevents to create/destroy per-meeting event processing queues
- handle all the non-streamer events
- if more than one backend is running, bbb-web splits the load in round-robin fashion by assigning an
instanceId. So individual backends only process redis events for the meetings matching the associated
ValidateAuthTokenRespis passed to backends as well, which is needed for the cases where you only have a backend, no frontends - for example dev environments that do not need to care about scaling
When you use
sudo bbb-conf --setip <hostname> or
sudo bbb-conf --restart,
bbb-conf will run
/etc/bigbluebutton/bbb-conf/apply-config.sh between shutdown and restart of the BigBlueButton processes. In this way, you can change configuration values of BigBlueButton, or use some of the helper functions in
apply-lib.sh. See Automatically apply configuration changes on restart.
BigBlueButton web application is a Java-based application written in Scala. It implements the BigBlueButton API and holds a copy of the meeting state.
The BigBlueButton API provides a third-party integration (such as the BigBlueButtonBN plugin for Moodle) with an endpoint to control the BigBlueButton server.
Every access to BigBlueButton comes through a front-end portal (we refer to as a third-party application). BigBlueButton integrates Moodle, Wordpress, Canvas, Sakai, MatterMost, and others (see third-party integrations). BigBlueButton comes with its own front-end called Greenlight. When using a learning management system (LMS) such as Moodle, teachers can setup BigBlueButton rooms within their course and students can access the rooms and their recordings.
The BigBlueButton comes with some simple API demos. Regardless of which front-end you use, they all use the API under the hood.
Redis PubSub provides a communication channel between different applications running on the BigBlueButton server.
When a meeting is recorded, all events are stored in Redis DB. When the meeting ends, the Recording Processor will take all the recorded events as well as the different raw (PDF, WAV, FLV) files for processing.
BigBlueButton Apps is the main application that pulls together the different applications to provide real-time collaboration in the meeting. It provides the list of users, chat, whiteboard, presentations in a meeting.
Below is a diagram of the different components of Apps Akka.
The meeting business logic is in the MeetingActor. This is where information about the meeting is stored and where all messages for a meeting is processed.
We have extracted out the component that integrates with FreeSWITCH into it's own application. This allows others who are using voice conference systems other than FreeSWITCH to easily create their own integration. Communication between apps and FreeSWITCH Event Socket Layer (fsels) uses messages through redis pubsub.
We think FreeSWITCH is an amazing piece of software for handling audio.
FreeSWITCH provides the voice conferencing capability in BigBlueButton. Users are able to join the voice conference through the headset. Users joining through Google Chrome or Mozilla Firefox are able to take advantage of higher quality audio by connecting using WebRTC. FreeSWITCH can also be integrated with VOIP providers so that users who are not able to join using the headset will be able to call in using their phone.
Kurento and WebRTC-SFU
Kurento Media Server KMS is a media server that implements both SFU and MCU models. KMS is responsible for streaming of webcams, listen-only audio, and screensharing. The WebRTC-SFU acts as the media controller handling negotiations and to manage the media streams.
Joining a voice conference
A user can join the voice conference (running in FreeSWITCH) from the BigBlueButton HTML5 client or through the phone. When joining through the client, the user can choose to join Microphone or Listen Only, and the BigBlueButton client will make an audio connection to the server via WebRTC. WebRTC provides the user with high-quality audio with lower delay.
Uploading a presentation
Uploaded presentations go through a conversion process in order to be displayed inside the client. When the uploaded presentation is an Office document, it needs to be converted into PDF using LibreOffice. The PDF document is then converted into scalable vector graphics (SVG) via
The conversion process sends progress messages to the client through the Redis pubsub.
Presentation conversion flow
The diagram below describes the flow of the presentation conversion. We take in consideration the configuration for enabling and disabling SWF, SVG and PNG conversion.
![General Conversion Flow](/img/diagrams/Presentation Conversion Diagram-General Conversion Flow.png)
Then below the SVG conversion flow. It covers the conversion fallback. Sometimes we detect that the generated SVG file is heavy to load by the browser, we use the fallback to put a rasterized image inside the SVG file and make its loading light for the browser.
![SVG Conversion Flow](/img/diagrams/Presentation Conversion Diagram-SVG Conversion Flow.png)
Internal network connections
The following diagram shows how the various components of BigBlueButton connect to each other via sockets.