Design Google Calendar! System Design Series: Episode 1

Welcome to my deep dive into designing Google Calendar from a system design perspective! In this video, I'll explore the architecture, components, and design principles. Whether you're a budding software engineer, a seasoned system designer, this video is for you. I'll break down the intricacies of its functional requirements, api and data modelling, and much more.
I'd love to hear your thoughts, questions, or experiences related to system design. Please drop a comment below and let's get a conversation going! Your participation enriches our community and helps us all learn more.
#systemdesign #softwareengineering #softwareengineer #softwaredeveloper
#interviewexperience #mockcodinginterview
Chapters:
00:00 Functional Requirements
02:30 High level design or low level Design
03:30 Api Endpoints and Database Schema
07:25 Data modelling
11:50 Simple Architecture Diagram
18:27 API Implementation
27:01 Handling Recurring Events
31:18 High level overview of Scalable Architecture
36:18 Outro

[@jayantgangwani7336]

Nice video, we can also add guest permissions

[@sreenidhisreesha]

Things i missed
1) Events table should have title and description
2) concept of multiple calendars (a separate calendar table and calendar column in events table)
3) Archiving old entries after a certain time (lets say move all past data to different store after 2 years)

[@_jatin_mittal]

can you talk about how would be shard the tables?

[@BeanOne-yg8vw]

Hey Shree, thanks for this video. Really liked how you keeped things simple and included both HLD and LLD.
As a beginner in system design, I would love to see in depth video about all the system design components with rational on when and where should be those used.

[@sreenidhisreesha]

i plan to add more soon. thanks for the comment. i’ll spend some more time on explaining the rationale