How to approach System Design?

System Design is tricky but it does not have to be difficult- be it a technical discussion at your workplace or your next big interview. Let's talk about how to approach System Design. Something I compiled from 10 years of my career.

What is System Design?

System Design is all about translating and solving customer needs and business requirements into something tangible. The output system could be an application, a microservice, a library, or even hardware.

There are a couple of approaches that we can use to design any system out there. Picking one over the other depends on the company you work for and the flexibility it provides.

The Spiral Approach

The Spiral Approach pans like a spiral in which you start with some core that you are comfortable with (database, communication protocol, queue. etc) and build your system around it. Every single component you add to the design is something that you are pretty confident about and can proceed with the added complexities.

For example:

• start with the database
• then add LB and more servers
• then add a queue for async processing
• then other services
• then add synchronous HTTP based communication between them

The Incremental MVP Approach

In the Incremental MVP-based approach we with a Day 0 design and then see how each component behaves at scale by dry-running it; after identifying the bottlenecks you fix them and re-iterate. You stop the iteration once you are happy with the final product. This kind of approach is typically seen in startups where they do not want to invest in architecture and quickly roll out features.

For example:

• start with Day 0 architecture of users, API servers, and DB
• then you add LB and more API servers
• then you add Read Replica on DB to support more reads
• then you split the service into a couple of microservices
• then you partition the DB to handle more scale

3 key pointers while designing systems

• Every system is infinitely buildable, hence fence it well
• Seek clarifications from your seniors
• Ask critical questions that challenge the design decisions

Here's the video of my explaining this in-depth ?? do check it out

System Design is tricky but it does not have to be difficult - be it a technical discussion at your workplace or your next big interview. In this video, I share the two approaches that I have been using to design scalable systems in the last 10 years of my career. I will also share the 3 key pointers to remember while designing any system that would help you keep your discussion crisp and focused.

Outline: - 00:00 Introduction - 02:41 What is System Design? - 06:02 The Spiral Approach to System Design - 07:27 The Incremental MVP Approach to System Design - 09:47 Key Pointers to remember during System Design

You can also

• Subscribe to the YT Channel Asli Engineering
• Download the notes
• Listen to this on the go on Spotify

Thank you so much for reading ?? If you found this helpful, do spread the word about it on social media; it would mean the world to me.

You can also follow me on your favourite social media LinkedIn, and Twitter.

Yours truly,

Arpit

arpitbhayani.me

Until next time, stay awesome :)

I teach a course on System Design where you'll learn how to intuitively design scalable systems. The course will help you

• become a better engineer
• ace your technical discussions
• get you acquainted with a massive spectrum of topics ranging from Storage Engines, High-throughput systems, to super-clever algorithms behind them.

I have compressed my ~10 years of work experience into this course, and aim to accelerate your engineering growth 100x. To date, the course is trusted by 600+ engineers from 10 different countries and here you can find what they say about the course.

Together, we will build some of the most amazing systems and dissect them to understand the intricate details. You can find the week-by-week curriculum and topics, benefits, testimonials, and other information here https://arpitbhayani.me/masterclass.