BigBlueButton Load Balancing

958 views
Skip to first unread message

Antony M

unread,
Apr 17, 2019, 4:19:41 AM4/17/19
to BigBlueButton-dev
Hi

Is it possible to implement Load Balancing in BBB that is running same session across multiple servers 

satyakam goswami

unread,
Apr 17, 2019, 5:11:20 AM4/17/19
to bigblueb...@googlegroups.com
On Wed, Apr 17, 2019 at 1:49 PM Antony M <tonm...@gmail.com> wrote:
Hi

Is it possible to implement Load Balancing in BBB that is running same session across multiple servers 

Hi,

BBB does not do  it natively but i have found some projects which are implementing the same 


this one i found  too http://www.bigbluemeeting.com/ looks like a  SAAS based version , have not tried them so no comments about them

thanks
-
Satya
Satyakam.dev | afrost.org | fossevents.in
** For all official purposes use my name as Satyakam Goswami **

Anatoliy Vinogradov

unread,
Apr 17, 2019, 5:30:42 AM4/17/19
to BigBlueButton-dev
We are also interested in finding a load balancer solution that will work correctly. But as far as we studied this question, at the moment there is no ready-made solution that will work with the latest version of bbb. I think it is necessary to wait for the bbb developers to release a version that will be minimally updated, and then you need to deal with load balancer. Until the end of work on the bbb, work on creating a load balancer is not relevant.
The project https://github.com/mconf/wiki/wiki has not been updated for a long time.
http://www.bigbluemeeting.com  does not accept new users. And judging by the description and video, they do not have a working solution.

среда, 17 апреля 2019 г., 12:11:20 UTC+3 пользователь satyakam goswami написал:

Chad Pilkey

unread,
Apr 17, 2019, 1:08:52 PM4/17/19
to BigBlueButton-dev
There's also different types of load balancing. There's the case where you want the same meeting spread across multiple servers in order to scale the size of a single meeting. The other scenario is where you have many meetings and you want to distribute them across a cluster of servers. To support the former would require changing the architecture quite a bit and isn't a use case that we are working towards yet. The latter is pretty simple at the heart of it, but the specific business needs are where it gets tricky. The amount of API calls that need to be supported are pretty small and we try our best to keep backwards compatibility so we don't break the various front-ends.
Reply all
Reply to author
Forward
0 new messages