Infrastructure that scales with load: behind the scenes
A hundred sessions at nine in the morning, three in the afternoon. Fixed servers meet that either expensively or with poor quality. How Dasmeet grows and shrinks its server pool with load.
Video conferencing load is not a flat line. At education providers it peaks in the morning and evening and drops at the weekend; at companies, quarter-end meetings pile up. With a fixed number of servers there are two ways to meet that wave: buy for the peak and leave servers idle most of the time, or buy for the average and lose quality at the peak. Neither is good.
The pool and the dispatcher
In Dasmeet, meetings do not run on a single BigBlueButton server but in a server pool. Every new meeting is placed on the most suitable server by a dispatcher that looks at the current load of each server in the pool. Participants never see this; the link is the same.
Growing
When the total load of the pool crosses a defined threshold, a new server is started, BigBlueButton is installed and configured automatically, and once the server passes its health check it joins the pool. This takes minutes, so the threshold is set to trigger before the peak. A margin of spare capacity is always kept in the pool to absorb sudden spikes.
Shrinking: the part that needs care
Shutting a server down is harder than starting one. A BigBlueButton server keeps processing recordings even after the meeting on it has ended; depending on the session length this can take minutes or hours. Shutting down a server whose recording has not been processed means losing the recording.
That is why the shrink step goes through a checklist: is there an open meeting on the server, is a recording waiting to be processed, have processed recordings been moved to permanent storage, has the transfer been verified? Only when everything checks out is the server first removed from the pool (it accepts no new meetings) and then shut down. No step is skipped; "probably done" is not enough.
The journey of a recording
A processed recording does not stay on the server; it is moved to permanent object storage, where the MP4 format is kept ready. So even if the server is shut down, the recording remains accessible. The download link you see in the panel or in your LMS points to that permanent storage.
What this gives you
Session quality does not drop at peak hours, you do not pay for idle capacity in quiet hours, and your recordings are safe regardless of a server's lifetime. You think about your session, not the infrastructure.
