Explore a conference talk from JSConf.Asia 2015 that delves into the structure of Node.js applications, comparing modular and monolithic approaches. Discover how the Node.js and npm ecosystem's culture of extreme modularity translates into real-world application construction. Learn from Tim Oxley, an Australian JavaScript developer and NodeSource employee, as he shares insights on avoiding premature modularization, deferring decisions, and building the simplest solutions that work. Gain valuable perspectives on managing complexity, avoiding over-engineering, and maintaining a balance between modular and monolithic structures in Node.js development.
Overview
Syllabus
TIM OXLEY MODULAR VS MONOLITH
GOOD MORNING!
WHO AM I?
NODE.JS: CULTURE OF EXTREME MODULARITY
ME IN 2012
RABBIT HOLES EVERYWHERE
NOTHING FOR FREE
MOST OF THE TIME
WHAT PROBLEM AM I TRYING TO SOLVE? 'IS THIS THE SIMPLEST THING THAT WILL WORK?
AVOID PREMATURE MODULARISATION
ASSUME YOUR FIRST ATTEMPT WILL BE BAD 60
CODE RETREAT
DON'T GET PRECIOUS ABOUT YOUR CODE
OVER-ENGINEERING: THE ADDING OF UNNECESSARY COMPLEXITY
COMPLEXITY KILLS PROJECTS
DEFER DECISIONS
DRAW IN PENCIL BEFORE YOU DRAW IN INK
ABSTRACTIONS DECREASE LOCAL COMPLEXITY WHILE INCREASING GLOBAL COMPLEXITY
BUILDING THE WRONG THING FOR THE RIGHT REASONS
BUILD THE SIMPLEST THING THAT WORKS?
FLAT IS BETTER THAN NESTED Z
At the statement level: avoid nested if/else. At the function level: avoid nested callbacks (i.e. Pyramid of doom) At the class level: avoid nested inheritance hierarchies. At the file level: avoid nested directories.
BUILD THE SIMPLEST THING THAT WORKS u
AVOID UNNECESSARY COMPLEXITY
THANK YOU!
Taught by
JSConf
