This message was deleted.

mediasoup works well but it's more bare bones. You're really on your own when it comes to scaling/infrastructure bit whereas livekit has those things covered with helm and good documentation. IIRC mediasoup also leaves all the messaging up to you so you'll need to build and support some sort of websocket thing.

👋 Shaoib, You are asking some good questions, but as Jonathan mentioned, I think livekit and mediasoup have different focuses. LiveKit is focused on being the best end to end WebRTC stack - from dev experience, client/server SDKs, to deployment and running in production. Things like running a high available multi-node setup are built in. Most of the WebRTC features (like simulcast) are supported by both libraries. We've layered a few things on top of it (like dynacast and adaptive stream) that makes it much easier to leverage these advanced WebRTC capabilities. In terms of performance, we strive to be the among the best. You can use the load-tester to get a sense of real-world performance. It's difficult to quote exact figures because multi-user experiences are very much dependent on your use case (i.e. publishing bitrate, how many streams would each user pull in at the same time, etc)

@dry-elephant-14928 @echoing-zebra-73489 Thank you guys for the information. Really appreciate it.