Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document architecture for Waveguide <=> Waveguide communication #8

Open
clone1018 opened this issue Mar 2, 2023 · 0 comments
Open
Labels
architecture documentation Improvements or additions to documentation

Comments

@clone1018
Copy link
Member

With our Janus FTL setup, we figured out that we could use janus servers to serve other servers, instead of viewers, effectively creating a mesh-like network of relays that deliver video to users. With Janus FTL, a streamer would stream to an ingest, and an edge close to the viewer would connect to that ingest to proxy the video to the viewer. Any additional viewers to that edge would utilize the same video stream as to not duplicate the connections.

With Waveguide the distributed setup can be very similar, just instead of utilizing FTL, utilizing our already existing WHEP output. A Waveguide server close to a user could negotiate with WHEP to have the stream sent to the Waveguide server, and then create another peer connection to the user to deliver the video to them. The benefits of doing it this way are a more reliable network connection DC to DC, and reducing the number of raw consumers on the Waveguide servers that are accepting inputs.

There's still more to brainstorm on how this would work.

@clone1018 clone1018 added documentation Improvements or additions to documentation architecture labels Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant