MicroManchester 2016 "Microservices from 30000ft: Organisation, Architecture and (Dev)Operations" with Nic Jackson
1 like738 views
The document discusses the impact of microservices on software delivery, emphasizing the importance of organization, architecture, and operations. It advocates for values such as small inter-discipline teams, continuous deployment, and user impact over customer requirements. Additionally, it highlights the necessity of technical leadership and the importance of change management in the implementation of microservices.
![Architectural/Design Skills
“If you can't build a [well-structured] monolith,
what makes you think microservices are the answer?”
Simon Brown
(bit.ly/1n7D0vp)
05/07/2016 @danielbryantuk](https://image.slidesharecdn.com/microservicesfrom30000ft-micromanchester-160705133533/85/MicroManchester-2016-Microservices-from-30000ft-Organisation-Architecture-and-Dev-Operations-with-Nic-Jackson-16-320.jpg)
MicroManchester 2016 "Microservices from 30000ft: Organisation, Architecture and (Dev)Operations" with Nic Jackson
- 1. Microservices from 30,000ft: Organisation, architecture and (Dev)Operations Daniel Bryant @danielbryantuk daniel.bryant@opencredo.com www.opencredo.com
- 5. 1. Lets start with a Story... OpENCREDO Went Skiing 05/07/2016 @danielbryantuk
- 6. 1. Lets start with a Story... OpENCREDO Went Skiing 05/07/2016 @danielbryantuk
- 8. @danielbryantuk • London Java Community Associate • Adopt OpenJDK and JSR • InfoQ Editor, DZone MVB, Voxxed 05/07/2016 @danielbryantuk • Chief Scientist at OpenCredo ü Transforming business through tech and teams ü Java, Golang, CI/CD, DevOps ü Microservices, cloud, containers
- 9. 2. Organisation: Conway was telling the truth... 05/07/2016 @danielbryantuk
- 11. Cross-functional Teams • Spotify (bit.ly/1C46ZKo) – Culture • Amazon (bit.ly/1F3Dgkm) – Communication • Gilt (gi.lt/1rgyWvO) – Strategic alignment 05/07/2016 @danielbryantuk
- 12. A Word of Caution • Divided Companies – Traditional ‘enterprise’ organisation – Command and control, specialised, division of labour – Predictable in stable environments – Six sigma, ESBs, and classical SOA • Connected Companies – Startups and forward-thinkers – Autonomous, fractal, service-focused – Adaptive in uncertain environments – Agile/lean, REST, and microservices 05/07/2016 @danielbryantuk
- 14. Organisational Values small inter-discipline teams over large homogeneous cabals products over projects user impact over customer requirements creating verifiable incremental value over adding features incremental transformationover big-bang “re-org” 05/07/2016 @danielbryantuk
- 15. 3. Architecture: think Micro, Think Macro, Think LEADERSHIP 05/07/2016 @danielbryantuk
- 20. Architecture, Minus the Ivory Towers • Technical leadership (bit.ly/1EUwpLl) • Communication (bit.ly/1Ia3u8o) • Empathy • ‘Just enough’ up front design 05/07/2016 @danielbryantuk
- 21. Migrating Architecture • Find seams • Measure toxicity of code • Standardisewhat matters (glue/infra) • Patterns (bit.ly/1GRch2v) – Big bang – Change via copy/extraction – Strangle 05/07/2016 @danielbryantuk
- 24. Architectural Values multiple cohesive services over a comprehensive application bounded contexts over a single domain model autonomous goal-driven leadership over anarchy or command and control implementing signals and performance indicators over measuring vanity metrics 05/07/2016 @danielbryantuk
- 25. 4. Operations: Automate everything (except the people) 05/07/2016 @danielbryantuk
- 26. Microservices… Macro Operations • Microservice Prerequisites (bit.ly/1wIjY58) – Rapid provisioning – Basic monitoring – Rapid application deployment • In a nutshell… – Technical part of DevOps – CI/CD 05/07/2016 @danielbryantuk
- 31. Failing to Prepare, is Preparing to… • Good monitoring and alerting • Practice failure (for real) – Chaos, Gamedays, DiRT sessions • Accountability – R.A.S.C.I. 05/07/2016 @danielbryantuk
- 32. Helpful Processes • BDD user journeys across system (via APIs) – …and individual services – Don’t forget ‘ilities’ (ZAP, bdd-security, Jmeter) • Brendan Gregg’s USE methodology – check utilization, saturation, and errors. • Symptom-based Monitoring (Ticketmaster) 05/07/2016 @danielbryantuk
- 33. Operational Values designing for failure over implementing extensive redundancy independent automated continuous deployment over coordinated manual big bang releases programmable infrastructure over manually-configured snowflakes Individuals and interactions over processes and tools symptom-driven monitoring over fault-report alerting 05/07/2016 @danielbryantuk
- 34. 5. Change management without Management double-speak 05/07/2016 @danielbryantuk
- 35. Change Management is Essential • Fair process (three ‘E’s) – Engagement – Explanation – Expectation • Leading change – Transformation is a process – Communicate, plan, evaluate, learn – Empowerment and empathy 05/07/2016 @danielbryantuk
- 42. NOTHS 2015 • An epic journey for all of the business • Docker is now proving itself in production – Reduced response time and footprint • Packaging applications is easier – So is experimentation… • Increased harmony between Dev and Ops 05/07/2016 @sheriffjackson | @danielbryantuk
- 44. Organisation, Architecture, Operations products over projects small inter-discipline teams over large homogeneous cabals multiple cohesive services over a comprehensive application goal-driven technical leadership over command and control automated continuous deployment over manual big bangs individuals and interactions over processes and tools 05/07/2016 @danielbryantuk