Integrate Redis and NGINX proxy/load balancer for backend services #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change integrates Redis into the session server backend, which allows us to horizontally scale that service, all the state will be stored in Redis, so the state is no longer tied to one machine.
It also integrates NGINX, which serves as a reverse proxy to our backend services, mediasoup server and session server. NGINX also load balances any number of instances we have for the session server.
How to spin up development environment:
How to emulate production environment (diff docker processes on local machine):
rtcServerDomain
tohttp://localhost:5000
in/client/src/utils/rtc-socket-client.ts
(will figure out a way to make this automatic based on environment)How to test with more sessionServer instances:
docker-compose up -d --scale sessionServer=3