peerjs VS mediasoup

this app is using peerjs to connect peers over a webrtc connection. check out thier docs for more info. with webrtc, things like file-transfer, should be very performant compared to cloud storage providers... especially over LAN. network speed doesnt seems to be an issue i have experienced.

I'm using the client-side PeerJS https://peerjs.com/ library for networking. As the name may imply, a direct connection is established between two peers using WebRTC via "handshake" through an intermediary server they host - and, they provide source for the server as well. I have found it to be quite reliable, thus far.

You kind of sound like a beginner. The browser APIs are a bit painful to work with. It might be easier to use PeerJS: https://peerjs.com/

If you want you can use Preact. PreactJS is a lightweight alternative to ReactJS, designed for high performance and compatibility. is often used in applications where performance is critical and has a small footprint.

This opens up a lot of neat possibilities, and fortunately I found a very easy JavaScript library for handling multiplayer called PeerJS. The way you can send packets from player to player is very simple and something even a beginner to JavaScript could understand.

You might be able to eliminate the VPS by making it P2P using something like PeerJS [1]. PeerJS provides a free shared connection broker server.

[1]: https://peerjs.com/

Note: peerjs is a good starting point!

We use peer.js module to create a WebRTC connection between clients

Now that we have all the required boilerplate we can start building the actual game. For the communications between peers we are going to use PeerJS a peer-to-peer library built on top of WebRTC.

Given the financial restraint, i was avoiding paid API's like twilio. I started looking at mediasoup https://github.com/versatica/mediasoup, but while implementing the SFU server, its seems a lot more involved. For ex, TURN and STUN, peers negotiating different video codecs, adaptively changing the quality of video etc. Is it usually this difficult to implement a video conferencing apps ?

This release ships lots of new features to the already comprehensive set of them. Currently, we offer several working tutorials on how to set up STUNner with widely used WebRTC media servers and other applications that use WebRTC in Kubernetes, such as: - LiveKit - Jitsi - mediasoup - n.eko - Kurento

Architecture WebRTC SFU (server with Selective Forwarding Unit). Can handle unlimited rooms without limits of time, each having 8+ users, potentially many as it is scalable. Routing is a multiparty topology, where each participant sends its media to the MiroTalk media server mediasoup and receives all other’s media from it. This version is Ideally suited for large group video conferences.

I started the MiroTalk P2P & MiroTalk SFU projects during the pandemic period (about 1+ year ago), not knowing anything about the WebRTC. Making often the video conferences with my colleagues and not wanting to depend on Zoom, Teams, Google Meet... I decided to do some research about how it works and from there MiroTalk was born :) I Giving to everyone the chance to have its own instance of MiroTalk, which can be customized as you like and run in any cloud, vps, server. If you're just starting out, I suggest you take a look at the MiroTalk C2C (New) code, which can be a good starting point to understand how the architecture WebRTC Mesh (P2P) works. Later you can also study how the WebRTC SFU (Selective Forwarding Units - I recommend mediasoup which I personally love) or MCU (Multipoint Control Unit) architecture works. I wish you all the best!

The "Mediasoup" project provides a high level JavaScript/TypeScript interface to the WebRTC APIs. The core logic of this project is implemented in C++/Rust. Consider taking a look at the project if you want an easy-to-use library instead of the low-level libWebRTC APIs. A notable project to mention is the Pion/webrtc project which has a Golang implementation of the WebRTC API. Of course, we should mention the rust port WebRTC.rs. Let’s keep all the rustaceans happy too!

Indeed, maddening, especially as the wonderful https://mediasoup.org/ is developed here. Europe will never have great tech companies when the answer seems to be throwing €€€ away instead of investing locally

Hello thedominux, Thanks for your interest in MiroTalk ;) MiroTalk SFU code is: - JAVA-SCRIPT: 85.2% - HTML: 10.0% - CSS: 4.5% And has built in mediasoup server, more details about: https://mediasoup.org/

Mediasoup