Комментарии:
All of the videos of this Indian guy on this channel are so pathetic, his design skills are so bad
ОтветитьAppreciate content, but little average api design
ОтветитьSomeone made this guy an EM lol
ОтветитьWhat tool for creating the diagrams are you using?
Ответитьsql db for tweets will be slow... timeline and feeds are different things
ОтветитьDoes anyone else think this interviewer is annoying?
ОтветитьWould it be good design to have the timeline as a queue. The queue would have a size that could perhaps be increased for people with lots of traffic. That way we store items that would be in the queue in the faster access database space and perhaps the stuff that would be maybe 3 queue away would perhaps be stored in a separate less frequently accessed storage (E3 perhaps?)
ОтветитьFor a facebook program manager that's a potato quality webcam.
Ответитьa failed interview for both interviewer and interviewee. such low quality
ОтветитьFor the timeline database, would it make more sense to store a list of tweet ids per user and then query the user database at runtime to compile the tweet text?
Ответить@exponent which tool is being used while answering the question?
ОтветитьThanks for the content! API structure is kind of out of common way to design restful apis. Don’t use verbs when it is possible.
ОтветитьThis is too basic design. Unless the candidate has less than 4 years of experience, this should get rejected
ОтветитьLost at influencer service/timeline generation piece. Please elaborate to me how these services work
Ответитьcool makes sense.....
ОтветитьCan definitely tell that this interviewee watched the Success In Tech version for this video. Like Chinese whispers, where unfortunately a lot of things are discussed at a high level and not enough rationale is explored.
I mean he even says Lady Gaga for his example for influencers, word for word as in the Success in Tech video. Just saying 🤷🏻♂️
its like only 24m system design interviews are like at least 35m
ОтветитьThis mock interview = 100% garbage
ОтветитьThis was pretty rough. If that’s what Exponent’s class teaches you then I’ll pass
ОтветитьThis design was so mediocre
Ответитьwhat is the meaning of mvp?
ОтветитьLooks like he didn't prepare well for the interview.
ОтветитьOne of the most horrible and unrealistic design interviews out there on the internet.
Asks almost no questions (fundamental to design interviews).
Not collaborative (also fundamental to design interviews).
Doesn't add a space in front of "(" when writing in English. Super distracting and unprofessional.
Breaks basic RESTful conventions with routes like /create/tweet
Very Bad idea giving name like gettweet ,createtweet . Basic naming of Rest API end points . Considering tweet as a resource just have GET and POST on it
ОтветитьTo me it sounded like..this is very very high level design ..but in my opinion he could have added some details around some of the below aspects or at least get clarification on requirements to trim out some of these..
1. Capacity planning
2. Type of DB and reason behind choosing that
3. Security aspects
4. High level db design
5. Tech stack ..for example.. aws s3 or cloud front or redis or Kafka etc
6. Scaling ..
7. peek load handling
8. caching mechanism
This is a bad video. I would reject this candidate. The API design is too abstract, the get API is not right. FB system design interviews are surely not this easy. This person is very lucky to be at FB.
ОтветитьI was expecting more out of this. This was a waste of my time.
ОтветитьWe should at least do some back-envelope analysis on the MAU, DAU, QPS,etc for the non-functional requirement. We should also make it more interactive, i.e. check the feedback of the interviewer before jumping into the details of the API's. Maybe ask the interview to see if he wants to see which one first: high-level design, API, or data model?
ОтветитьWhat app is it in the background?
ОтветитьI like it 👍 What IDE do you use for the design prototyping?
ОтветитьThe geographic load balancing to different API servers part made no sense to me. When a user makes a request to a load balancer, they make an API request specifically to the load balancer and receive from it directly, so the don't make contact with the API servers at all. If you put the API servers in different regions, that would only be with respect to the load balancer, not the user themselves, so it wouldn't help at all since the load balancer is still in the same region. You'd need to do the geographic routing first before the load balancing step to do this properly, aka a traffic manager.
ОтветитьHe didn't do any capacity calculations such as bandwidth and storage, is that ok for these interviews?
ОтветитьThis interview feels like it is given by a New Grad Software Engineer.
ОтветитьProbably been asked on previous videos, but what software/website is used as the design visualization/scratchpad for the interviewees?
Ответить