HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
donnemartin
system-design-primer
Python2017–2026
donnemartin / system-design-primer

system-design-primer

Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.

60Distinct people
68Mentions
3Explicit recommenders
377.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Ah sorry about that. I think my comment came off as a bit rude after reading it back to myself. Backend development means so much nowadays I think it would be hard for someone…

willmeyers used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year68 dated mentions

Observed mentions: 2017-03-09 09:53:27 UTC to 2026-09-01 20:08:01 UTC.

0510152017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 5 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 3 submissions, 3 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 14 mentions; 1 submissions, 13 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC752
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC624
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC12210
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC13112
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC633
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC14113
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC523
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC110
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC312

What Hacker News says

14 sources
I've certainly been where you are. It definitely sounds like you need a job change, but your next company should be selected with care. > I don't have good grades in my undergrad Don't furnish that information. If the company asks you, bow out - it's an absurd question when you have 5 years of experience. A masters won't help you much and I wouldn't recommend it in your situation. It's the kind of thing a person thinks about when they feel stuck - I've had the same impulse at every career junction. > Should I work on solving LeetCode questions, and aim to get into FAANG companies I'd certainly recommend LeetCode, but not just for interviews. There are benefits to it that nobody mentions: your initial code correctness, your debugging skills, your communication skills, and your familiarity with your programming language all go up. I just we
Read the rest
nt through this process and the time investment has paid off quite well. I used to hate LC and thought I wasn't capable of landing any job, let alone a top tier job. FAANG is good for compensation, but not necessarily the most exciting work, so keep that in mind. There are many non-FAANG companies that are good catches. teamblind.com is a great resource for interview tips, if used carefully. Expect months-long practice and to do a lot of interviews. Rejection is just part of the process. Interview with companies you haven't heard of/don't care much about first. Respond to random recruiters who reach out. Don't forget to study for behavioral questions (STAR method) and system design (https://github.com/donnemartin/system-design-primer). For practical LeetCode tips - expect to complete a few hundred of them if you want to get into a top-tier shop. Speak out loud and explain as if you're in an actual interview. Timegate yourself: 7.5 minutes for easy, 12.5 minutes for medium, 20 minutes for hard. These are very aggressive times. If you haven't finished in that time, look at the solution, take notes, and understand it. Here's a Python script I wrote to help myself with this process. `pip install rich` should take care of the only external dependency. This script randomly selects LeetCode question numbers and creates a markdown file for note-taking. When I failed a question, I would stick it in `attempted` and it would come back up eventually. #!/usr/bin/env python import random import sys from pathlib import Path from rich.console import Console LC_COUNT = 2218 TIME_LIMITS = { "Hard": "20:00", "Medium": "12:30", "Easy": "7:30", } crushed = {} mediocre = {} attempted = {} short_list = { # Blind 75 76, 102, 105, 124, 128, 143, 152, 153, 198, 207, 208, 211, 212, 213, 230, 238, 252, 269, 271, 295, 300, 322, 323, 371, 417, 422, 424, 435, 449, 1143, } all_lc = {num for num in range(1, LC_COUNT + 1)} untried = all_lc.difference(crushed) lc_options = short_list or attempted or untried or mediocre lc_options = lc_options.difference(crushed) if len(sys.argv) > 1: num = sys.argv[1] else: num = random.choice(list(lc_options)) console = Console() def user_input() -> str: return console.input(prompt="[bold blue]>>>[/bold blue] ") console.print("LC:", num) base_path = Path.home() / "LC/" for existing_path in base_path.glob(f"*/{num}-*.md"): console.print("File already exists:", existing_path) exit() difficulty = "" while difficulty not in TIME_LIMITS: console.print(f"Difficulty {list(TIME_LIMITS.keys())}:") difficulty = user_input().strip().capitalize() name = "" while not name: console.print("Name:") name = user_input().strip().replace(" ", " ") url_name = name.lower().replace(" ", "-") path = base_path / f"{difficulty}/{num}-{url_name}.md" template = f"""# Problem: {name.title()} https://leetcode.com/problems/{url_name}/ *Difficulty:* {difficulty} *Status:* Untried *Time:* ? left out of {TIME_LIMITS[difficulty]} minutes # Notes: # Attempts: ## Time: O(?) Space: O(?) ``` ``` # Solutions: ## Time: O(?) Space: O(?) """ if path.exists(): console.print("File already exists:", path) else: console.print("Creating file:", path) with open(path, "w") as outfile: outfile.write(template) console.print("Done", style="bold green")
In Ask HN: What should I do next for my career?
willmeyers·Aug 16, 2022Recommendation phrase
Ah sorry about that. I think my comment came off as a bit rude after reading it back to myself. Backend development means so much nowadays I think it would be hard for someone to publish a general book on it. But maybe someone else has found something that I'm unaware of. I think you'll have the best luck collecting some general resources about different subjects. Here's some resources that I recommend flipping through. - Any up to date book on the programming language of your choice - Any up to date online course of the programming language of your choice - https://hpbn.co/ (networking) - Build APIs You Won't Hate (api design) - https://github.com/donnemartin/system-design-primer (system design) - API Design Patterns by Geewax (somewhat opinionated, but overall good resource for api design)
In Ask HN: What is the proper way get into back end development?
Best way to learn is by working with someone experienced. Or just use mature solution like Rails for example it solves most of typical problems and has easy itegrations. If you need more flexibility then maybe Node.js or other ecosystem is better. Generally theme about architecture is called System Design and there are resources to learn it for interviews/learning purposes but most of it only is applicable at very big scale and you might never need it. Read "Designing Data Intensive Applications" and look into [1] if still interested. IMO better to invest time into data design/querying (caching) so that you won't think you need some vodoo to handle your traffic. Like 90%+ of sites/apps don't have 1000req/second and this should be handled by Python on Arduino so as long as your DB design is good you are fine. For async processing it's wort
Read the rest
h taking a look into Temporal [2] as it looks as promising alternative to job ques and cronjobs. I can also recommend [3] to learn some cloud patterns [1] https://github.com/donnemartin/system-design-primer [2] https://temporal.io/ [3] https://docs.microsoft.com/en-us/azure/architecture/patterns...
In Ask HN: Who do you talk to about system architecture and design?
Work through these books, then you start looking at any random app or system and can start from there: - System Design Interview – An insider's guide: https://smile.amazon.com/gp/product/B08CMF2CQF - System Design Interview Vol 2: https://smile.amazon.com/System-Design-Interview-Insiders-Gu... - Designing Data-Intensive Applications: https://smile.amazon.com/gp/product/1449373321 - System Design Primer: https://github.com/donnemartin/system-design-primer Especially: https://github.com/donnemartin/system-design-primer#how-to-a... - The Architecture of Open Source Applications: http://aosabook.org/
In Ask HN: What is best way to do hands-on practice for system design?
> there's no way to do a "cracking the system design interview" the way you can with coding problems I'd disagree: - System Design Interview – An insider's guide: https://smile.amazon.com/gp/product/B08CMF2CQF - System Design Interview Vol 2: https://smile.amazon.com/System-Design-Interview-Insiders-Gu... - Designing Data-Intensive Applications: https://smile.amazon.com/gp/product/1449373321 - System Design Primer: https://github.com/donnemartin/system-design-primer Especially: https://github.com/donnemartin/system-design-primer#how-to-a...
In Ask HN: What is best way to do hands-on practice for system design?
Increase your monthly income or lower your monthly spending. Easiest is to find a new job. If you have 14 YOE as developer you should be able to find a higher paying job as long as you've continually grown your skills. Put your résumé on Hired.com and put in a desired salary of $200K to gauge companies' interest then adjust up or down as needed. Do a few practice interviews on Pramp. Read up on System Design here https://github.com/donnemartin/system-design-primer. Watch YouTube videos on DS&A and practice coding on LeetCode.
In Ask HN: How do I Stop Living Paycheck to Paycheck?
I went through Facebook and Google interviews (as well as others) back in early 2019 and eventually accepted an offer from FB for an M1 role (was previously a senior manager at a smaller company). At FB I had a coding slot, a couple of system design slots, and I think three behavioral. At Google I didn't get any coding, but it was because of a higher level role (L7) that I was interviewing for (and did not get). For context, I hadn't coded professionally for ~8 years at that point, so part of the prep was getting back into that. Also, I never took any algo classes in college 15-20 years earlier, so that was another challenge. I actively avoided big tech companies for years due to difficult interviews and low confidence that I would pass, not to mention a general attitude of why the hell should I spend all this time preparing for something
Read the rest
that does not reflect the day-to-day reality (and I still hold this view strongly). But as I learned more about compensation opportunities, I decided to bite the bullet and go for it. I quit my job and spent 3-4 months preparing mostly full-time, while also lining up interviews. Pro-tip here: if you get Google interviews, start them way in advance of all others. Their process is insanely long and after 3 months of interviewing, re-interviewing, getting downleveled, changing hiring managers, etc. I dropped out of the process because I was already sitting on two offers. For comparison, Facebook took 2 weeks from starting to schedule interviews to offer. For coding, I picked up Python - unless you know something else really well, it's IMO the best language for interviews (never used it professionally, but had not great experience from a few years back interviewing in my language of choice of C#). I got a few books to learn and refresh on the data structures and algorithms: Algorithm Design Manual (good reference, but I didn't end up having time to really go through the material there), Cracking the Coding Interview (skimmed, basic to intermediate stuff here) and Elements of Programming Interviews in Python (skimmed, intermediate to advanced stuff here). I got lucky and recalled the general approach to my FB coding problem from the EPI book. Now for the most important part - create an account on leetcode.com and start practicing. I would recommend focusing on easy and medium levels. I imagine managers would generally get medium-level questions, engineers are expected to solve medium and advanced. My approach was to identify a list of topics, then for every topic read ADM, then CtCI, then EPI, then solve a few easy and medium LC problems, rinse and repeat. I've seen folks recommend that solving ~200 LCs is enough to get comfortable. I didn't have as much time as I would've liked and did about 60. The general idea is to be able to pattern match (e.g. this type of problem needs a hash table, this is a graph problem, etc), some people focus on memorization - I think that's a terrible approach, but most companies do end up asking questions from LC (except Google apparently). With limited time I was flying through topics towards the end, would not recommend. I did pay for Leetcode Premium for a few months - lets you focus on the types of problems that specific companies are asking, was worth it for me. Coding aside, I actually spent most of my time preparing for system design interviews. Found that my knowledge of building large systems was not nearly sufficient for interviews. My approach here was to first purchase this course: https://www.educative.io/collection/5668639101419520/5649050... and read through the basics section. It really is basic, so I was supplementing by diving deep into each topic on my own. It's still a pretty useful resource for getting an idea of what breadth I should be targeting, along with https://github.com/donnemartin/system-design-primer. Then I read Designing Data-Intensive Applications (amazing book, but incredibly dense), and finally went through all the concrete design problems on the Grokking course as well as watched a bunch of relevant Youtube videos. Felt a lot more comfortable towards the end and I think did alright on those slots. I think the concept of consistent hashing rings came up in literally every single system design interview, so be super familiar with it and various implementations. My interview experience with these was that the really senior folks were more into depth, and the less senior ones focused on breadth. I'd suggest going for both, e.g. the Grokking course and System Design Primer have decent coverage of breadth of topics, but are absolutely not enough for depth. Maybe you could skate by on breadth alone (I'd say it's more valuable than depth), but why take the chance. Some examples of going deep I encountered were talking about different kinds of load balancers and balancing mechanisms, different ways of traversing a consistent hash ring, different failure modes and workarounds in distributed systems. I originally wasn't going to memorize common latency numbers, but it came up during Google's prep session (they offered one with an interviewer, to give feedback) when I embarrassingly struggled to convert 1 Gbps to 125 MB/s. Of course most rounds were non-technical, so I prepared for those with as many questions I could come up with in advance and recalling various scenarios in detail - super important not to assume that these will just come to you during an interview. I also put together a 65-page summary doc of all the stuff I was reviewing, most of it system-design related, that I went over frequently to refresh myself. Finally, the Blind app and levels.fyi were instrumental in opening my eyes on the crazy compensation at those companies and I was able to do a better job negotiating with this info. I was fortunate that I had the ability to take the time off to focus on interview prep, and I would 100% not have passed the interviews without it. My cynicism about the whole process only grew, as exactly nothing from my prep was relevant to the day-to-day job at Facebook. ¯\_(ツ)_/¯
In Ask HN: Applying for EM Roles at FAANG?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.