Suppose the average API response is 100ms.Suppose 300KB is tolerable (Performance).Suppose how many interactions occur in a day.Suppose the Daily Active Users(DAU)/Monthly Active Users (MAU) of the service.What is the future roadmap? - List of TODO and NOT-TODOs.What is the shining point from service & also the Developer Experience (DX) - Developer can also contribute a lot of improvement.

What is the MVP - List of Core features like Core APIs, Core interactions, and Core interfaces.What’s the volume of the service and how many team members.Is SEO a concern? Yes - we support Server-Side Rendering (SSR) or else Single Page Application (SPA) is good enough.Things mostly are Mobile-first, do we need a design for a Desktop?.

What’s the relationship with native apps? If you already have an app, is the web application just the replica? Or is it the liter version(MVP version of the app)? If no native apps, then create with PWA or with hybrid technologies?.

What is the goal of the web service or web application?.

What is the core spec (based on the MVP)- What are the problems we need to handle, What are the edge cases, and What the tricky part is.

How would you separate them into parts and put them together (UI/logic) - Separate the state & logic and sync the UI with the state.

What is the MVP( Minimum Viable Product) - List of Core features like Core APIs, Core interactions, and Core interfaces.

What is the data flow (API) / User flow - List of all API’s i.e what kind of APIs we need and general user flow, where will the user click, and what will happen.

What is your non-functional goal of the feature?.

What is the basic goal of the feature? - Basically, what do you want to achieve.

The NOT-TODO should be also listed down, to show that we are aware of the not-todo but due to time constraints, we will not be able to do that.

List up the TODO and NOT-TODO( Check with the Interviewer ).

The scope cannot be a perfect service, but the core parts should appeal to an interviewer within 45 minutes.

Don’t do the parts that you are not good at. So we need to pick those parts in which we are more confident. Well, we cannot design a perfect system because there will be limited time i.e only 45 mins to 1 hour. We must make sure what the interviewer wants to know and check with them whether we understand the problem statement correctly.Īfter understanding the problem, we need to decide what the scope is going to be. 1) Understand what it isįirstly, we need to understand the problem. These tasks are applicable for designing a product or a feature from a front-end perspective. Let’s list down the major tasks involved for a given system design problem. Major Tasks Performed During the System Design Process

Data - This is the management of the information and data flow.

Interfaces - This is the shared boundary across which the components of a system exchange information and relate.

Components - This provides a particular function or group of related functions.

A combination of the modules makes up the system.

Modules - These are components that handle one specific task in a system.

We can use flowcharts to represent and illustrate the architecture.

Architecture - This is the conceptual model that defines the structure, behaviour, and more views of a system.

The purpose of the System Design process is to provide sufficient detailed data and information about the system and its system elements to enable the implementation consistent with architectural entities as defined in models and views of the system architecture. System Design is the process of designing the elements of a system such as the architecture, modules and components, the different interfaces of those components and the data that goes through that system.

Justinmind loading animation