8 Most Important System Design Concepts You Should Know
Вставка
- Опубліковано 9 лют 2025
- Get a Free System Design PDF with 158 pages by subscribing to our weekly newsletter: bit.ly/bbg-social
Animation tools: Adobe Illustrator and After Effects.
Checkout our bestselling System Design Interview books:
Volume 1: amzn.to/3Ou7gkd
Volume 2: amzn.to/3HqGozy
The digital version of System Design Interview books: bit.ly/3mlDSk9
ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.
Problems:
1. Read heavy systems: 0:22
2. High write traffic: 1:14
3. Single point of failure: 2:16
4. High availability: 2:54
5. High latency: 3:26
6. Handling large files: 3:59
7. Monitoring and alerting: 4:27
8. Slow DB queries: 4:56
no music, no bs. thank you!
Exactly. I don't want music or stupid personality gimmicks. I just want clear infographics and deep knowledge summarized so I can take first notes and make a framework to build the rest of my research on.
criminally underrated content. Keep it up man
Your vlogs are a bomb must watch before system design interview
I am pleasantly surprised that these strategies are essentially the same, in principle, as the ones that I employed over a decade ago when I was architecting systems. I don’t feel quite as old after watching this video :)
Your videos are very informative and go to our cloud infra in the next level.
Really packed with a lot of info and great graphics make it easier to remember. Thanks!
Beautiful rundown! Thank you!
Great animation. I need to practise this too🔥
easy to understand. i feel so smart
A+ as always
Regarding Observability you can consider mature tools such as Datadog that enables having all the Observability data in one platform.
Thank you for doing this!
Hello, I'm new here. I hope to learn a lot from you.
Which tool do you use to create animations for system designs?
which software you are using to create this animation?
Wow! Awesome!
great content
What a video masterpiece
I felt so stupid seeing all those techs used in this modern era of software development, well that means more rooms to grow!
Please make your books to video versions.
I like it❤
please do one for each
Can you also add when to use views and materialized views to this
How to create the flow chart animtion like 0:16 ?
Adobe Illustrator and After Effects
ms paint and a lot of time
@@hpr895 Oh dang, you hate life lol
The problem of these solutions is how they also defeat the solution being produced
Take the most common scenario. A small team of devs builds a solution that is predicted to experience high number of reads or writes or requests etc.
The more complexity they introduce into the code to solve these problems
The bigger the future dev team will need to be to maintain , move, add features etc.
Will the commercials necessarily be there to support that dev team? (in most examples, no it won't)
the use of libraries compound the problem. Because it adds to the knowledge/study and experience load upon individual devs.
AND you have now got a product full of dependencies with its future challenges of tech debt, obsolescence and the dreaded .dll update hell.
A most vicious circle.
Top!!!
At what level should a full-stack developer start learning about system design? Junior, Mid-level or Senior?
when u wish
💜💜💜💜
Hlo, Sir, Upload the Real Data science. Roadmap. How to become Data Scientist. And about skills Required to Develop in This Domain. Do this. ❤
but i see you all for your saas buisness just go on one server for the start and dont over complicate !
In the context of interviews I don't like that you mention specific brand names in such an introductory level video. Any specific product mention (like Redis, Cassandra or Kafka) in a real world interview will almost inevitably lead to a question about their details and/or comparison with alternative products - which would be an automatic failure for someone who needs a video like this to familiarize themself with the concept.
I feel that’s always going to depend on the interviewer. As long as you can explain the technology I have nothing against people mentioning it. I might also point out that we use something else and ask if they know about it and then discuss similarities and differences. That gives me an idea of how the person thinks thought problems.
If the idea of questions about a specific package/product extremely relevant to your interview intimidate you…
you are not ready for that job.
You don't need to use products' names during the interview only because there are some in this video. I'd treat this as a set of somewhat structurized hints, to dig deeper for details, not as an instruction how to pass an interview.
you could do all that junk and install all those annoying things ooooooor you could just use rails.
tell me you've never worked at scale w/o telling me you've never worked at scale
@@rogertunnell5764 wtf is this reddit or something... so you've written an app in rails8 (like me) or are you just repeating bs someone told you...
@@SteveHazel Well, I'm a principal software engineer so I don't need to repeat what someone told me. I've lived it. I've built systems that required asynchronous processing, data partitioning, caching, autoscaling, etc. The fact that you're arguing about "an app" and thinking that "an app" is written in a framework means you probably wrote some monolithic, dynamically typed, single instance toy that handles requests for a few hundred users. Go work on a multi-national ERP or any big data system where terabytes of data are processed per day, requiring HIPAA, SOC2, or ITAR compliance and tell me how that rails app holds up. How are you going to run ruby on embedded sensors? How are you going to run it on mobile apps, or tvs? There are 100s of reasons to need more than a web framework. You're punching above your weight, jr.
@@rogertunnell5764 whatev. you don't know me i don't know you.
"Just use rails"
Yeah, lemme just rewrite our entire system with another language and framework...