More than adding CPU to one box
Horizontal scaling introduces a load balancer, shared operational conventions, monitoring and recording considerations. Standardising each media node makes capacity additions and replacements safer.
Keep stateful services visible
Greenlight, PostgreSQL, Redis and recording data have different lifecycle needs from media nodes. A cluster design should identify where each component lives, how it is backed up and what happens during a node failure.
Automate repeatable deployment
The official BigBlueButton documentation points experienced large-scale operators toward automation such as Ansible. Optional engineering can scope a consistent node baseline, but ongoing cluster operations remain the customer’s responsibility.
The operational reality
BigBlueButton capacity depends on how people use media. Hardware specifications help narrow the choice, but your own load test, monitoring and failure plan turn that choice into a production design.