Telegram is a essence massaging application that allows users to send message to each other and even to groups of people. There’s a lot of big scale.so a lot of users on this application.so i guess for purpose of this interview let me kind of ask you some questions about this make sure that I really understand that what you want me to design. This telegram is pretty big,is pretty complex sophisticated. So let’s see if I can narrow this down and ask you some questions.
First off in term of use cases . again i mentioned it is basically i can sending and receiving messages.So i think the primary use cases that i want to think about is i want to send messages and i want to check messages and read my messages,so there is also groups.so maybe question to you.you know add all those the base use cases that you’d like me to cover in term of the functionality the system.and what about the groups.
Okay so now just one to one messages make sense.in term of this messages.just make a assumption here.really for now we just talk about text messages.you know they can to help telegram itself allows to send a large things too but purpose for this we just kind of talk about text messages sending and receiving those.
okay so in term of functional requirements,sending and receiving.what i’d like to do as i am going though this if that’s okay.it’s i am not really much of a front-end person.i am sort of worked more
On the back-end side of things.so i wouldn't be able to speak a lot about sort of how this shows up in an application.so the entry point into the system might be APIs essentially.And i can think of
Four APIs which we can go into a little bit later that might reflect that. So i wanted to check with you is it okay if we sort of use APIs as the entry point into the system design.
So the one thing i think about a lot of non-functional requirements.is scale.how big is do you want to the system be? Maybe tell me a little a bit about how many what kind of scale,how many messages do you want to be able to handle in the system.
