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)
yes I believe this design is great for team meetings and we would need a DL strategy for large team meetings. I would guess we should have a separate table for DL with a 1 --> M relation with Users table. We can also have a separate table for events_DL to handle the API call. The strategy for recurring meetings was open ended a bit as both the strategies had CONS. But Strategy 1 was sure a choice I would go to and may be look at sharding the db to avoid loading it up with many records as the DB grows. Thanks much for the design
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.
are you explaining with the norms of a distributed system? If yes what are some of the best protocols to implement as part of this distributed system? What are some important resources you can suggest for implementing a distributed system like this?
![[Front-End System Design] - Google Calendar](http://i.ytimg.com/vi/leo1FZ6vu1I/mqdefault.jpg)
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)
yes I believe this design is great for team meetings and we would need a DL strategy for large team meetings. I would guess we should have a separate table for DL with a 1 --> M relation with Users table. We can also have a separate table for events_DL to handle the API call. The strategy for recurring meetings was open ended a bit as both the strategies had CONS. But Strategy 1 was sure a choice I would go to and may be look at sharding the db to avoid loading it up with many records as the DB grows.
Thanks much for the design
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.
i plan to add more soon. thanks for the comment. i’ll spend some more time on explaining the rationale
Awesome video, thanks
Glad you liked it!
are you explaining with the norms of a distributed system? If yes what are some of the best protocols to implement as part of this distributed system? What are some important resources you can suggest for implementing a distributed system like this?
what's the purpose of sending heart beats ? and what exactly do app tiers mean here ?
can you talk about how would be shard the tables?
Nice video, we can also add guest permissions
thank you!