System Design Interview: Design Calendar Application
Vložit
- čas přidán 27. 07. 2024
- Don't leave your system design interview to chance. Sign up for Exponent's system design interview course today: bit.ly/3DsYvTa
Watch our mock system design interview. Angie asks Connor a question on how to design a relational model for a calendar application.
Chapters -
00:00:00 - Introduction
00:00:45 - Clarifying questions
00:01:18 - Data types
00:02:37 - Design
00:17:40 - Follow-up questions
00:22:25 - Interview analysis
Watch more videos here:
- Amazon SDE answers binary tree question: • Amazon Software Engine...
- Google SWE answers algorithms interview question: • Google Software Engine...
- Google TPM answers Tiktok system design interview question: • System Design Mock Int...
- Microsoft SWE answers algorithms interview question: • Microsoft Software Eng...
👉 Subscribe to our channel: bit.ly/exponentyt
🕊️ Follow us on Twitter: bit.ly/exptweet
💙 Like us on Facebook for special discounts: bit.ly/exponentfb
📷 Check us out on Instagram: bit.ly/exponentig
📹 Watch us on TikTok: bit.ly/exponenttikttok
ABOUT US:
Did you enjoy this interview question and answer? Want to land your dream career? Exponent is an online community, course, and coaching platform to help you ace your upcoming interview. Exponent has helped people land their dream careers at companies like Google, Microsoft, Amazon, and high-growth startups. Exponent is currently licensed by Stanford, Yale, UW, and others.
Our courses include interview lessons, questions, and complete answers with video walkthroughs. Access hours of real interview videos, where we analyze what went right or wrong, and our 1000+ community of expert coaches and industry professionals, to help you get your dream job and more!
#systemdesign #calendar #software #engineeringmanagement #tech #entrepreneurship #exponent #tpm - Zábava
Don't leave your system design interview to chance. Sign up for Exponent's system design interview course today: bit.ly/3DsYvTa
This was more of a Database design, obviously not a system design video.
The question was to define a relationship model for a calendar. I guess that’s why he concentrated on that part.
yup i feel the same, also it went too fast into the schema design. wondering would it be better to discuss the storage before starting on schema. like why sql over no sql. also talk more about what is a "calendar" object. what is an "event" etc
You cannot do a meaningful system design unless you discuss what to be store in database. how to handle data...
Thanks Guys, great job.
Thanks a lot for great informative video on system design. Please keep posting more video on Low Level Design as well as System Design. I think we have seen none of Low Level design video. Hope to see these videos in future. Thanks
Hey @Chandra, do you have an example low-level design question you'd like to see here?
@@tryexponent First of all thank you so much for providing the great content via your Amazing Channel. I would like to have example like FoodDeliveryApplication, Library Management System, BookMyShow(Ticket booking System), Online Chess Game etc which includes all the class diagrams and relationship[p between the classes and using design and Solid principle to carry out the overall architecture of the System.
It would be great if you can cover the recurring events along with RSVP so if user has rejected an event invite or any particular recurring event, it should not ne be visible in its calendar
Thnax for posting such an informative video, I'm really noob at system design 😅
I don't think this is really a system design, rather database design. There's a clear cut difference between the two imo
Hi guy!! Here from Peru. You have now a new follower on your channel. I hope you are fine and I hope you make more videos about this
What tool you guys are using for designing these flows
?
What tool is Connor using to type out that table schema?
It's called Whimsical! We use it across all of our mock system design videos
@@tryexponent I do not see a similar option in Whimsical.. Is it a template? or Project? how to add lists
@@sukhmeetchhabra9218 it is wireframe
@@tryexponent Cool! Thanks for sharing!
thank you for posting. but wondering if this is the way do go during a system design interview. I could be wrong, but I was looking for some discussion about the definition of a "calendar" or "event" object before goes into the schema design. also some discussion about the scale of the project. and how users interact with the APIs (also some api design). Just briefly discuss about all of these issue, and then pick one thing to dive deep.
I also stopped after watching the half video. This is not the right way.
In the start of the interview itself, interviewer's expectations was to to design a relational model for the calendar. So IMO they did what is asked for.
Takes querying 5 tables to server 1 common request like view my events today? Talking about DB model & relationship without access pattern first just looks wired
Its a DB design not system design please rename the title
May I ask one question: Which tool did the interviewee used to draw those diagrams so fast ?
Pretty sure that's Whimsical. Great tool 👌
Why is he storing notifs in a table ? Wouldn't making it functional be better?
How we can keep recurring meetings, it will be huge data to save if we save each event of reccuring event as a new row, Is there any other way to just save as small as possible data for recurring events, Also i would like to see how will be the HLD for the same. Thanks in advance!!
I think we need to have a Series table and series_id (it can be null tho) referenced by Events.
That clarifying questions only lasted a minute, and they were all provided by interviewer? Then he dived right into data model, and no flow from the requirements mentioned by interviewer?
What is the editor used in this demo
Whhimsical.io
How would it handle recurring events?
How is it stored in database?
Same question here! Would love to see a video on how to think about recurring events.
When I tried this exercise myself, I was thinking about adding an enum for occurrence on the Event model. That way, I can easily map days to a time in the future.
YEARLY == 365 Days
Daily == 1 Day
Weekly == 7 Days
Monthly == 31 Days etc...
But then I looked at google calendar and saw how they handle, recurring events, and made me think that if on the Event model, add a boolean (reoccurs) if that is checked, create a new Model (RecurringEvent).
Which has an enum if the recurrence is daily, weekly, monthly, annually. If it is custom there can be more options for how often to do the reminder the event and what not
which tool he is using ?
would like to know too, see a few interviews, but they never talk about the tools they used
this must be for a junior position, I mean 2 mins in, you can already tell if the person has experience or not, you can ask about if there is a join that is heavy on one dataset vs the other but that's the extend of signal you can get. senior position is more free form to let the candidate "shine"
Same thoughts.
Can you elaborate on “join that is heavy on one dataset”? What does that mean/what should one be looking for
@@AbstractAbsorption that also didn't make sense to me, I guess he means interviewer could ask that or interviewee could bring it up? Either way, it's depends on what queries you wanna support too
Still don't understand why we use a junction table for a one-to-many relationship...
I don't think the design would work in production. Most of all, there was no proper solution about scaling up. No solution to method of sharding
Calender is linked to a user. Events are linked to a particular calender . A notification is linked to a particular event. So we dont need userId info in notification table.🤔
There might be specific situations where linking notification directly to user would perform faster queries if you are doing analytics. It all depends.
Too much normalization, no api discussion, no scaling .. notification discussion.
Hey I'm preparing for APM roles, is there anyone who wants to join to take interview of eachother.
A serial uuid?
too much information on schema.. would have been better if we start with the functional and non functional requirements and then adjust the schema.. this is wrong way to do the design as too much time spent on entities and relationships which is changing all the time we get a question.
such a poor video. Where is the system design. This video just talks about defining tables, which is like the bare minimum that anyone is tech, should be able to do.
Did anyone else find it alarming that the candidate launched into data design before even saying a word about concrete use cases and how the data will be used? The approach in this interview is backwards, IMO
The question asked was to provide the database design.
Using join tables means many to many. But it seems wrong to me that event has many calendars. I assume that each calendar is for specific types of events like job, entertainments etc. So, events couldn't have mixed domains. Another thing is about teamUser table. The role should not belong to teamUser but to user him self. Generaly, this whole relationships model based on join tables only is confusing and wrong. No constrains mentioned. Where is cascade where is not? Very poor design.