Building Platforms, Breaking Code: How your org chart wrecks everything!

Transcript

2. Michael Meelis Hey there! Checkout my LinkedIn page. Here you can read what I did and how I came here. @michaelmeelis
3. Michael Meelis Platform Engineer • What do I do? • Bootstrap / Design Automation • Use Case • RTL • Terraform
4. Devops is a methodology, not a role
5. Building Platforms, Breaking Code How your org chart wrecks everything!
6. Welcome to court
7. Court Our Court • Jury Examine the laws that have been broken • Executioner Execute the guilty • Judge Review the law
8. I AM THE LAW!
9. Court - Judge The Laws Without any customers you don't have a functioning product, rendering your effort useless Murphy’s Law If something can go wrong, it will Brook’s law Adding manpower to a late project makes it later Amdahl’s law The maximum speedup of a system is limited by the portion that cannot be parallized Knuth’s optimization principle Premature optimization is the root of all evil Moore’s law The power of computers per unit costs doubles every 24 months Pareto Principle (80 – 20 rule) For many phenomena, 80% of consequences stems from 20% of the causes.
10. Pareto’s Principle For many phenomena, 80% of consequences stem from 20% of the causes.
11. Conway’s Law Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.
12. Jury
13. Court - Jury Conway’s law • Communication is everything • High bandwidth of communication lost when you divide • Good • But also bad
14. Developers, Developers, Developers – Steve Balmer
15. Communication, Communication, Communication, Communication - Michael Meelis C4 Architecture
16. Court - Jury 3 Steps 1. Ignore Conway’s law 2. Accept Conway’s law
17. Court - Jury In ye old days Front-end Front-end Front-end DBA OPS Backend Backend Backend Team A Team B Team C
18. Court - Jury In ye old days UI UI UI DB OPS API API API App A App B App C
19. Court - Jury 3. Inverse Conway Maneuver Organizations should evolve their team and organizational structure to achieve the desired architecture. The goal is for your architecture to support the ability of teams to get their work done - from design through to deployment - without requiring high-bandwidth communication between teams - Nicole Forsgren
20. Court - Jury Microservices Front-end Front-end Front-end QA Backend Backend Backend Team A Team B Team C QA QA Devops Methodology
21. Court - Jury Microservices UI UI UI Infra API API API App A App B App C Infra Infra
22. Court - Jury Hashicorp
23. Court - Jury Lessons learned • Org chart needs to be flexible • Change the org chart because, • Org chart is your Product • Not just software!
24. Court - Jury Lessons learned
25. Court - Jury Domain Driven Design The structure and language of the code should match that of the business domain - Eric Evans
27. Court - Jury Domain Driven Design Support Raise Log in to Ticket Account Buy Pay with Ticket Account Booking Go to Platform
28. Court - Jury Domain Driven Design Platform 1 Platform 2 Platform 3 Platform
29. Platform Platform Time Shift Cleaner Shop Cafe Destination Train Ticket Price Passenger Shop Product Customer
30. Generic Supporting Core
31. Executioner
32. Court - Executioner Finally! Where 50 people plan how 5 people will do the work, and finally, we know the secret of how to solve Conway’s law, concluding this talk!
33. Court - Executioner Mashing it up Conway’s Law C4 Architecture Domain Driven Design
34. Court - Executioner Inverse Conway Maneuver Organizations should evolve their team and organizational structure to achieve the desired architecture. • Design the org, design the product • Ultimate Communication bandwith • Resilliant for the future • BizDevSecOps Pros • Big curve Enterprise • Time and effort Cons
35. Court - Executioner Hashicorp - Devops
36. Court - Executioner Hashicorp - Security
37. Court - Executioner Hashicorp - Communication
38. Court - Executioner Domain Driven Design The structure and language of the code should match that of the business domain • Document your product • Gain insight • Unified language Pros • Difficult to start • Complex overall Cons
39. Michael Meelis Executioner • Domain Driven Design • Seperated Terraform Repo’s • Teams per Domain
40. Michael Meelis Hey there! Checkout my LinkedIn page. Here you can read what I did and how I came here. @michaelmeelis
41. This document is confidential and personal to its recipients © ITQ 2023 Postel’s law Be conservative in what you send Be liberal in what you accept
42. This document is confidential and personal to its recipients © ITQ 2023 Questions?