![]() Low latency: The system should be extremely low latency, offering a real-time chatting experience.Availability: High availability is desirable, but not as crucial as consistency.Consistency: Above all else, the system should be consistent users should see the same chat log on all devices.Protected: Messages should be encrypted during transit.File agnostic: Users should be able to send pictures and videos as well as text messages.Archived: Messages should be stored for later viewing.Multi-functional: Service must support one-on-one and group chats.Online: Messages must be sent and received via the internet.Messages should only be accessible by those included in the conversation. Conversations can be one-on-one or can be group chats with many members. Design a chat service like Facebook Messenger or WhatsAppįor this question, you’ll design a service that allows users to chat with each other over the internet. Some older companies will have legacy systems, but microservices can function in parallel to legacy code and help refresh the company architecture as a whole.įor more information on how ML can improve your SDI performance, check out How Machine Learning gives you an edge in System Design.ġ. Unlike the monolithic architectures of tech companies in the past, microservices allow smaller, agile teams to build independently from the larger system. Know your architectures: Most modern services are built upon a flexible, microservice architecture. This will demonstrate that you’re not just prepared for current solutions but future solutions as well. State your assumptions before outlining the componentsĭiscuss emerging technologies: Conclude each question with an overview of how and where the system could benefit from machine learning.Ask clarifying questions to show the interviewer how you’re viewing the question and your knowledge of the system’s needs. At each decision point, list at least one positive and negative effect of that choice.Īsk your interviewer to clarify: Most system design questions are purposefully vague. Narrate any trade-offs: Every system design choice matters. The listing process lets the interviewer see your planning skills and correct any possible misunderstandings before you begin the solution. Start each problem by stating what you know: List all required features of the system, common problems you expect to encounter with this sort of system, and the traffic you expect the system to handle. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |