Database Design of Zoom System Design
- Zoom’s database design is about user management and recording functionalities.
- A user table that should store necessary user information, while a separate recording table manages recorded sessions and required information.
- Permissions are set to record access tables to facilitate user access to recordings.
Zoom uses public clouds like AWS o host metadata of meetings, web applications and other services. It uses AWS for real-time traffic. For educational users zoom expands to Oracle Cloud.
In this Design:
- AWS hosts the tables for Users, Meetings, and Recordings.
- Oracle Cloud Database hosts the table for Educational Resources.
- Users table is shared between AWS and Oracle Cloud Database.
- Meetings table includes details about scheduled meetings, with a foreign key reference to the Users table for the host.
- Recordings table stores information about recorded meetings, linked to the Meetings table via a foreign key.
- Educational Resources table contains details about educational materials, with an uploader_id referencing the Users table.
Designing Zoom | System Design
Creating an app like Zoom may seem simple from the user’s perspective, but in reality, it’s a complex task involving hundreds of software engineers working for years. Zoom, like other similar apps, requires careful planning and design to provide seamless video conferencing services worldwide. This article explains how Zoom works and how it handles a lot of cases.
Important Topics for the Zoom System Design
- Requirements of Zoom System Design
- Capacity Estimation
- High-Level Design of Zoom System Design
- Low-Level Design of Zoom System Design
- Microservices used in Zoom System Design
- API Design of Zoom System Design
- Database Design of Zoom System Design
- How Zoom handle Scalability?