WebRTC Architecture that keeps working when us-east-1 goes down
This week AWS had an outage in the northern Virginia region , probably the most commonly used region and many of the most popular services in the world were affected. It was at least the third time in five years that AWS’s northern Virginia cluster, known as US-EAST-1, contributed to a major internet meltdown. Every service is different, and nowadays, with so many dependencies and coupling, it is hard not to be affected by an incident like this. However, specifically for WebRTC platforms, it should be relatively straightforward to handle cases where one specific AWS region goes down. Basic WebRTC Architecture The basic architecture of most of WebRTC platforms comprises four components: Load balancing service: The client application’s initial point of contact, selecting the appropriate media server for a session. Database: Stores server information (status, load, location) and session-to-server mappings, often using a fast database like Redis. Signaling service: Manages...