3 THE PROMISE OF MICROSERVICES decision autonomy ease of scaling the organisation language & framework independence more digestible code easy to experiment and explore easier transition from legacy code …
7 S TA R T W I T H A T E A M A ND SOM E CO D E THE PR OB L EM Limit to a number of people. Nice and easy collaboration. Fast development. Don’t try to jump to any other structure until you really have to.
9 C O N C AT I N C O D E We know how to do it by know. There are tools to help. Some organisations stay in this state for a long time. THE PR OB L EM No real autonomy.
11 C O N C AT I N T H E A P P 0 1 0 1 1 1 0 1 Still very common and the are usually module systems to help, like NPM. Some organisations stay in this state for a long time. THE PR OB L EM Framework / language lock-in.
1 3 C O N C AT O N T H E S E RV E R There have to be strong reasons to do this, but can make sense during a transition period between technologies. THE PR OB L EM Usually very complicated and fragile setup with technology lock-in.
1 5 C O N C AT I N T H E B R O W S E R Essentially the same setup from an organisational perspective as with one team, but can scale to crazy number of people. And also gives autonomy to experiment and innovate. THE PR OB L EM The only way to do it now is an iframe.
1 9 H O W D O E S I T L O O K I N P R A C T I C E ? Header Fragment Cart Fragment Base Assets Fragment Tracking Fragment } Not every fragment has to be visible
2 2 IT GETS WORSE If you need to just render some text with links in a style consistent with the rest of the website, it’s kind of bad to expect to build all of the React stack.
2 8 GOALS AND NON-GOALS • Future-compatible • High performance • Pre-made hooks for popular frameworks GOALS • 100% feature parity with the spec • High-level API N O N - G O A L S