This video covers the essentials of system design. I’ll explain how to define the requirements and goals of your system, document the discovery process, and understand the motivations and constraints behind your design decisions. I’ll also discuss estimations, scheduling constraints, and managing uncertainty, as well as technical implementation. I’ll share tips for effective diagramming and discuss challenges specific to SaaS and traditional companies. This is a comprehensive overview of system design best practices!
▬▬▬▬▬▬ Resources & References 📕 ▬▬▬▬▬▬
- ByteByteGo Newsletter: https://blog.bytebytego.com/
- PlantUML: https://plantuml.com/
- Mermaid: https://mermaid.js.org/#/
- C4 model: https://c4model.com/
- Fundamentals of software architecture book: https://www.oreilly.com/library/view/fundamentals-of-software/9781492043447/
- Notability app: https://notability.com/
- Concepts app: https://concepts.app/en/
Sources:
- Traceability matrix sheet: https://www.researchgate.net/figure/Requirements-traceability-matrix-for-online-shopping-system_tbl4_280083523
- Feedback loop drawing: https://web.archive.org/web/20160413143321/http://www.strategicality.com/hey-thats-my-graphic-turning-image-theft-into-links/
▬▬▬▬▬▬ Chapters 🕐 ▬▬▬▬▬▬
00:00 - System design is not just about interviewing! 00:57 - My experience designing systems 02:23 - This is not a recipe 03:46 - Defining “the what” 06:14 - Documenting the discovery process is critical 06:49 - Defining “the why” 09:59 - Defining “the when” 11:20 - Estimations & scheduling constraints 14:08 - Understanding uncertainty 16:36 - Defining “the how” 17:41 - Technical problems are easy! 18:45 - You rarely design on a blank slate 20:06 - System design in SaaS companies is different 20:34 - System design in traditional companies 23:43 - Big tech problems are relatively simpler problems 24:46 - My diagramming process 29:45 - The 2 laws of software architecture 31:08 - System design is an optimization problem 33:21 - Why do we do system design? 34:47 - Architecture diagrams reduce abstraction 35:26 - Essential diagram types 37:16 - The software that I use for diagramming 38:21 - The important layers in a system design diagram 42:41 - Don’t diagrams become obsolete quickly? 44:42 - Where should we store documentation & diagrams? 45:44 - Conclusion
▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬
- Twitter: https://twitter.com/bassemdy
- GitHub: https://github.com/link-
- LinkedIn: https://www.linkedin.com/in/bassemdghaidy
- Facebook: https://www.facebook.com/BassemDy
- Blog: https://blog.bassemdy.com
▬▬▬▬▬▬ Support the channel 💜 ▬▬▬▬▬▬
Every little bit helps ✨
- Join the journey on Patreon: https://www.patreon.com/glich_stream
- 1 time support: https://www.buymeacoffee.com/glich.stream
#glichstream #softwareengineering