Download as PDF, PPTX
Uploaded byTimothy Oxley
Modular vs Monolith
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.
More Related Content
Modular vs Monolith
- 1.
- 2.
- 3.
- 4.
- 5.
- 6. ME IN 2012: “AVOIDFRAMEWORKS” 🗿
- 7. ME IN 2012: “BUILDLIBRARIES INSTEAD” 🎊
- 8. BUILDING A LIBRARY ▸Reusable! ▸ More Robust! ▸ Higher Quality Code! ▸ Better Documentation! ▸ Better Tests! ▸ Open Source!
- 9. ME IN 2012: “LIBRARY-FIRSTDEVELOPMENT” 🎵
- 10. ME IN 2015: “YESBUT, THERE ARE SOME MAJOR CAVEATS…” 😮
- 11.
- 12. LIBRARIES ARE A LOTOF WORK 💝
- 13.
- 14. MOST OF THETIME: YAGNI 🚮
- 15.
- 16. WHAT PROBLEM AMI TRYING TO SOLVE? IS THIS THE SIMPLEST THING THAT WILL WORK? 🛀
- 17. NOT EVERYTHING NEEDSA MILITARY-GRADE SOLUTION
- 18. ENGINEERS HAVE A STRONGURGE TO OVER-ENGINEER
- 19. ENGINEERS OFTEN BUILD THINGSWE WANT, RATHER THAN THINGS WE NEED
- 21. ENGINEERS OFTEN SPEND HOURSTO SAVE MINUTES
- 22. OVER-ENGINEERING: THE ADDING OFUNNECESSARY COMPLEXITY 🚼
- 23.
- 24. OVER-ENGINEERING IS MORE COMMONTHAN UNDER-ENGINEERING 📠
- 25.
- 26. OVER-ENGINEERING IS MORE COSTLYTHAN UNDER-ENGINEERING 💰
- 27.
- 28. THE WRONG STRUCTURECAN BE MORE COSTLY THAN NO STRUCTURE AT ALL 🎷
- 29. STRUCTURE CAN BEMORE EASILY EXTRACTED FROM LOOSE STRUCTURE. INCORRECT & COMPLEX STRUCTURE NEEDS TO BE TORN DOWN BEFORE BUILDING NEW STRUCTURE
- 30. ASSUME YOUR FIRST ATTEMPTWILL BE BAD 💩
- 31. MAKE DECISIONS THAT AREEASY TO REVERSE
- 32.
- 33. DRAW IN PENCILBEFORE YOU DRAW IN INK ✏
- 34. BEST WAY TOPLAN 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
- 35.
- 36. PUBLISHING TO NPMIS NOT THE ONLY WAY TO DO “MODULAR” CODE. 📡
- 37.
- 38.
- 39. ABSTRACTIONS DECREASE LOCAL COMPLEXITY WHILE INCREASINGGLOBAL COMPLEXITY 🍩
- 40. BUILDING THE WRONG THINGFOR THE RIGHT REASONS 🏭
- 41. FLAT IS BETTER THANNESTED 🌈
- 42. FLAT IS BETTERTHAN 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 THINGTHAT WORKS 🔑
- 44. THE SIMPLEST THING ISPROBABLY FLAT 🗺
- 45.
- 46. THE SWEET SPOTIS SOMEWHERE IN THE MIDDLE
- 47.
- 48.
- 49.
- 50.
- 51.
- 52. MAKE SURE WHATYOU’RE BUILDING ACTUALLY MAKE SENSE AND IS USEFUL IN PRODUCTION.
- 53.
- 54.
- 55. BUILD THE SIMPLEST THINGTHAT WORKS 🎷
- 56.
- 57.