Modular vs Monolith
3 likes1,492 views
The document discusses the tradeoffs between modular and monolithic software architectures. It advocates starting with a monolithic approach and progressively modularizing over time to avoid unnecessary complexity. The key is to build the simplest thing that works and avoid over-engineering solutions. Functions, statements, files, and folders can provide adequate structure at first before prematurely abstracting into packages or libraries.
Modular vs Monolith
- 1. MODULAR VS MONOLITH TIM OXLEY
- 5. ME IN 2012: 👶
- 6. ME IN 2012: “AVOID FRAMEWORKS” 🗿
- 7. ME IN 2012: “BUILD LIBRARIES INSTEAD” 🎊
- 8. BUILDING A LIBRARY ▸ Reusable! ▸ More Robust! ▸ Higher Quality Code! ▸ Better Documentation! ▸ Better Tests! ▸ Open Source!
- 9. ME IN 2012: “LIBRARY-FIRST DEVELOPMENT” 🎵
- 10. ME IN 2015: “YES BUT, THERE ARE SOME MAJOR CAVEATS…” 😮
- 12. LIBRARIES ARE A LOT OF WORK 💝
- 14. MOST OF THE TIME: YAGNI 🚮
- 15. gunshowcomic.com
- 16. WHAT PROBLEM AM I TRYING TO SOLVE? IS THIS THE SIMPLEST THING THAT WILL WORK? 🛀
- 17. NOT EVERYTHING NEEDS A MILITARY-GRADE SOLUTION
- 18. ENGINEERS HAVE A STRONG URGE TO OVER-ENGINEER
- 19. ENGINEERS OFTEN BUILD THINGS WE WANT, RATHER THAN THINGS WE NEED
- 21. ENGINEERS OFTEN SPEND HOURS TO SAVE MINUTES
- 22. OVER-ENGINEERING: THE ADDING OF UNNECESSARY COMPLEXITY 🚼
- 24. OVER-ENGINEERING IS MORE COMMON THAN UNDER-ENGINEERING 📠
- 25. xkcd.com
- 26. OVER-ENGINEERING IS MORE COSTLY THAN UNDER-ENGINEERING 💰
- 28. THE WRONG STRUCTURE CAN BE MORE COSTLY THAN NO STRUCTURE AT ALL 🎷
- 29. STRUCTURE CAN BE MORE EASILY EXTRACTED FROM LOOSE STRUCTURE. INCORRECT & COMPLEX STRUCTURE NEEDS TO BE TORN DOWN BEFORE BUILDING NEW STRUCTURE
- 30. ASSUME YOUR FIRST ATTEMPT WILL BE BAD 💩
- 31. MAKE DECISIONS THAT ARE EASY TO REVERSE
- 33. DRAW IN PENCIL BEFORE YOU DRAW IN INK ✏
- 34. BEST WAY TO PLAN FOR INEVITABLE, UNEXPECTED CHANGES: DON’T INVEST TOO MUCH IN SOLVING TODAY’S PROBLEMS THE PERFECT SOLUTION FOR TODAY MAY BE A TERRIBLE SOLUTION FOR TOMORROW TREAD LIGHTLY
- 36. PUBLISHING TO NPM IS NOT THE ONLY WAY TO DO “MODULAR” CODE. 📡
- 39. ABSTRACTIONS DECREASE LOCAL COMPLEXITY WHILE INCREASING GLOBAL COMPLEXITY 🍩
- 40. BUILDING THE WRONG THING FOR THE RIGHT REASONS 🏭
- 41. FLAT IS BETTER THAN NESTED 🌈
- 42. FLAT IS BETTER THAN NESTED APPLIES AT ALL LEVELS ▸ At the statement level: avoid nested if/else. ▸ At the function level: avoid unnecessary nested calls ▸ At the class level: avoid deeply inheritance hierarchies. ▸ At the file level: avoid deeply nested directories. ▸ At the project level: avoid deeply nested projects.
- 43. BUILD THE SIMPLEST THING THAT WORKS 🔑
- 44. THE SIMPLEST THING IS PROBABLY FLAT 🗺
- 46. THE SWEET SPOT IS SOMEWHERE IN THE MIDDLE
- 47. A MODULITH?
- 48. MONOLITH FIRST 🏛
- 52. MAKE SURE WHAT YOU’RE BUILDING ACTUALLY MAKE SENSE AND IS USEFUL IN PRODUCTION.
- 55. BUILD THE SIMPLEST THING THAT WORKS 🎷