decentraland / decentraland/catalyst
LiveKit Resiliency
- Dominant language
- TypeScript
- Stars
- 52
- Forks
- 56
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
In production currently, there are 2 flavors of LiveKit: Cloud and Hosted service.
This still represents a weak failure point if the LiveKit cloud stops working. A disaster recovery process or a fallback mechanism should be implemented to mitigate this. For the time being, this can be accomplished by changing the branch to comms-v2 and starting the node on P2P comms but this requires maintaining 2 branches of the catalyst-owner repo.
Contributor guide
Research direction
No files or tests are named. Start by reviewing the catalyst-owner repository, the comms-v2 branch, and how the node is started with P2P comms. Done should mean an agreed disaster-recovery or fallback path for Cloud and Hosted LiveKit that avoids maintaining two branches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100