docs(streaming): add single-server implementation plan
This commit is contained in:
@@ -147,6 +147,7 @@ Stream realtime events:
|
||||
- This backend currently acts as a control plane (commands, session state, credentials, events), not a full media plane/SFU.
|
||||
- Running live transport + fan-out + recording on the same web server is possible for small loads but introduces significant CPU, RAM, and network egress pressure under concurrency.
|
||||
- For larger deployments, use a dedicated media plane (managed or self-hosted SFU + recorder) and keep this service focused on auth/session/control APIs.
|
||||
- For a pragmatic prototype path that keeps media on the current server, see `docs/streaming-on-web-server-plan.md`.
|
||||
|
||||
### API Docs
|
||||
OpenAPI docs are generated from Zod/OpenAPI definitions:
|
||||
|
||||
Reference in New Issue
Block a user