robfig
We've had a good experience with this approach, although it is far from plug-and-play. We do have to identity and patch items in Chromium/WebRTC & the server (Pion) interaction to get our video quality up to compete with Zoom/Teams/Meet. We are able to effectively compare video quality across these providers and expect to reach their video quality with this stack.
Disclaimer: I work on Roam's Chat, AI, and API.
[1] We are currently in closed beta so there's not much there at the moment.
Catalyst – Web Component System by GitHub
KittyCAD
Grizzly: Deploy and Observe as One
Csproto – CrowdStrike's Protocol Buffers Library
Will advanced reactors solve nuclear’s problems?
Linux tracing systems and how they fit together (2017)
Jo – a shell command to create JSON (2016)
Docker for Mac Without Docker Desktop
Gokrazy – A Native Go Userland
Why Bazel is written in Java
Hello-World.rs
Chrome: Record, replay and measure user flows
Pop OS – System76
Subgraph OS: Adversary resistant computing platform
Fork Yeah the Rise and Development of Illumos
The 5-Hour CDN
Open Decision-Making (2014)
But service discovery and zero downtime upgrades are not that hard to implement and maintain. Our company's implementations of those things from 12 years ago have required ~zero maintenance and work completely fine. Sure, it uses Zookeeper which is out of vogue, but that also has been "just working" with very little attention.
A thought experiment where we had instead been running a Kubernetes cluster for 12 years comes out pretty lopsided in favor of the path we took for which one minimizes the effort spent and complexity of the overall system.
And don't get me started on the local USPS.