livekit
libwebrtc
Our great sponsors
| livekit | libwebrtc | |
|---|---|---|
| 8 | 1 | |
| 7,042 | 41 | |
| 4.6% | - | |
| 9.8 | 1.8 | |
| 7 days ago | almost 2 years ago | |
| Go | Rust | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
livekit
-
Jitsi Meet Flutter SDK
Zoom does use a custom protocol. This is why it doesn’t work nearly as well when you take a call in the browser client. Not because WebRTC isn’t up to the task, but because Zoom hasn’t invested in it.
Ignoring costs, while having someone host infra for you will always be easier than managing it yourself, I think we’ve really improved the DX of hosting your own WebRTC infra with LiveKit: https://github.com/livekit/livekit
- Video streaming in golang
-
Scaling WebRTC with Go: how we built a distributed mesh network for 100k-person events
https://github.com/livekit/livekit/blob/master/pkg/service/egress.go looks like the meat of this
-
Insights into quality engineering at any of the video streaming companies?
You might be able to learn a bit from digging into https://docs.livekit.io/
-
livekit-server VS livekit - a user suggested alternative
2 projects | 27 May 2022
As mentioned in the description, the project is not DISCONTINUED, it has just moved.
- LiveKit – Open source, high performance WebRTC infrastructure
- LiveKit – open-source, high performance WebRTC infrastructure
libwebrtc
-
LiveKit – open-source, high performance WebRTC infrastructure
I'd recommend Rust for your shared client core, even though for short-term practicality you probably have to keep using Google's C++ WebRTC library, because translating your existing high-level client code to safe Rust would be easier than translating it to reasonably safe C++.
If you're interested in pursuing this, the best starting point I've found for using the WebRTC C++ library from Rust is this: https://github.com/arcas-io/libwebrtc So far it looks like it only works on Linux and Mac.
What are some alternatives?
webrtc - A pure Rust implementation of WebRTC
ringrtc
OvenMediaEngine - OvenMediaEngine (OME) is a Sub-Second Latency Live Streaming Server with Large-Scale and High-Definition. #WebRTC #LLHLS
ion - Real-Distributed RTC System by pure Go and Flutter
datachannel-rs - Rust wrappers for libdatachannel
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
matchbox - Painless peer-to-peer WebRTC networking for rust wasm (and native!)
jitsi - Jitsi is an audio/video and chat communicator that supports protocols such as SIP, XMPP/Jabber, IRC and many other useful features.
livekit-server - Scalable, high-performance WebRTC SFU. SDKs in JavaScript, React, React Native, Flutter, Swift, Kotlin, Unity/C#, Go, Ruby and Node. [Moved to: https://github.com/livekit/livekit]