I am working on a longitudinal series of projects that heavily involve the use of Jitsi, especially in educational settings. This is for large scale environments that have highly demanding loads, and are intended as Zoom replacements in the USA and worldwide. This is just one of a number of components.
Today was great to finally reach the 1,000 simulated video users load test basic baseline. Next goal is 5,000+, and then adding in additional features and still trying to keep it all working on this scale (recordings, transcriptions, closed captioning, intricate chat options, complex permissions managements, file management, and much more). Great things happening!
Due to Jitsi’s modular, opensource, and highly configurable nature, there are many different architecture variations available when deploying a Jitsi ecosystem. This posting attempts to summarize, some more theoretical for the sake of discussion and analysis, a wide range of variants to consider for different implementations. Which Jitsi Architecture Variant to choose is based on each individual's specific scope and budget. Each successive variation tends to be more complicated than the prior variant. Note that these are NOT Jitsi official variations or terminology. These variation distinctions were created by Hawke Robinson as an attempt to bring some order to the many different potential approaches, and increase clarity when considering scalability, features, and budget constraints.
