When the traffic in the server increases and the server resources max out, we
would need more servers to meet the demand. If the volume of traffic remains constant, we can easily
add more servers to meet the demand. However, if the volume of traffic changes frequently, a
workable solution must be found. An autoscaling solution must be used in this situation, in which
the servers are spun up or down based on the traffic volume.
Key Components needed in
Autoscaling:
A single shard with a single Jitsi Meet, multiple Jibri, and JVB will be generated.
Numerous shards will be present, each with multiple jitsi Meet and Multiple Jibri and JVB.
UNRC wanted to use Jitsi for their online classes. While installing jitsi is an easy task, scaling it to handle large number of users is a different scenario. Keeping in mind the scenario of 10K+ concurrent student, we scaled the jitsi accordingly. We helped them with following jitsi services:
While everyone was shifting virtually, our valuable client got an idea to develop a virtual event platform. We used jitsi for 121 networking, group networking, sponsor networking with along with other live streaming tools. We helped them with following jitsi services:
Turkey university want to integrate jitsi with their existing moodle based LMS. They were expecting load of 20k+ students at a time. We help them to achieve using below services
Focus on your business growth and leave development and configuration to us.
For a small number of concurrent conferences, a single server Jitsi installation is sufficient. We need to add secondary servers to have unlimited concurrent conferences.
As an open source software, Jitsi can be scaled easily using sharding.
Autoscaling is a method where based on the main CPU consumption, secondary servers will be created to meet the demaind. It helps to optimize the server cost
Indeed, Jitsi can be scaled for on-premise use.
Focus on your business growth and leave development and configuration to us.
Contact us