scaling out architectural decision making
play

Scaling out architectural decision making OReilly Software - PowerPoint PPT Presentation

@patkua Scaling out architectural decision making OReilly Software Architecture Conference Berlin (November 2019) The first bank youll love @patkua Banking, this beautiful @patkua Chief Scientist, former CTO #leader #coach


  1. @patkua Scaling out architectural decision making O’Reilly Software Architecture Conference Berlin (November 2019)

  2. The first bank you’ll love @patkua

  3. Banking, this beautiful @patkua

  4. Chief Scientist, former CTO #leader #coach #architect #developer #life-long-learner #author #cto We’re hiring in Barcelona , Berlin , & Vienna & NYC! https:/ /n26.com/jobs/ @patkua

  5. Chief Scientist, former CTO thekua.io/evolarch thekua.io/twtl thekua.io/retrobook @patkua

  6. Course: Tech Lead Skills for Developers http:/ /thekua.io/tech-lead-course @patkua

  7. Level A curated newsletter for leaders in tech Up http://levelup.thekua.com @patkua

  8. Why scale What What did decision did we do? we learn? making? @patkua

  9. Why scale decision making? @patkua

  10. Our context: Hypergrowth @patkua

  11. @patkua

  12. @patkua

  13. New York Berlin Barcelona @patkua

  14. “ Hypergrowth feels like you’re building the rocket as its flying @patkua

  15. @patkua

  16. @patkua

  17. Decisions @patkua

  18. Decisions Design Architecture Easier to change Harder to change @patkua

  19. Decisions Code layout within a service BE <-> FE error standard Method/function design Sync versus Async Library Standard “across” services Easier to change Harder to change @patkua

  20. Decisions Decision Buy-in Time Quality @patkua

  21. Decisions Fast AND good @patkua

  22. Decisions How we used to make decisions… @patkua

  23. Meetings Information Pain Points Locations Visibility @patkua

  24. Why scale What decision did we do? making? @patkua

  25. Practices Working Architecture RFCs Groups Guild @patkua

  26. R equest F or C omments @patkua

  27. RFCs @patkua

  28. Organic Introduced Confusion adoption RFCs @patkua

  29. Refactoring RFCs @patkua

  30. Refactoring RFCs @patkua

  31. Refactoring RFCs @patkua

  32. ? RFCs @patkua

  33. 83 RFCs @patkua

  34. Practices Working Architecture RFCs Groups Guild @patkua @patkua

  35. Working Groups @patkua

  36. Working Groups @patkua

  37. NO Design by Commi tu ee Informed Consulted Speed Working Groups @patkua

  38. O fu en about Many Multiplier gaps Listening for perspectives pain points Working Groups @patkua

  39. Example: Error Handling Working Groups @patkua

  40. Example: Error Handling iOS Android Web Internal Service A Service B Service C Service D Working Groups @patkua

  41. Example: Error Handling JSON? Structure What details? Already translated? Working Groups @patkua

  42. Example: Error Handling Result: Adoption of RFC7807 - Problem details object (type, status, detail, userMessage, instance) - Content-Type = application/problem+json - Only used for 400 and 500 responses - Use of 207 (batch request/response) Working Groups @patkua

  43. Practices Working Architecture RFCs Groups Guild @patkua

  44. Architecture Guild @patkua

  45. What? - Representatives across the entire tech - Entire company wide cross cutting topics - Decision making authority Architecture Guild @patkua

  46. Who? iOS Android Web Security Data Internal Tools SRE BE QE Staff Engineers Segment Location (BCN, NYC) Architecture Guild @patkua

  47. Example: Updating Tech Radar Architecture Guild @patkua

  48. Example: Security Scanning in CD Pipe Architecture Guild @patkua

  49. Why scale What What did decision did we do? we learn? making? @patkua

  50. Learnings @patkua

  51. Learnings Meetings Information Pain Points Locations Visibility @patkua

  52. Learnings Listen Observe Refactor @patkua

  53. Learnings Iterate Listen Observe Refactor @patkua

  54. Questions? @patkua We’re hiring in Barcelona, Berlin, Vienna & NYC! https:/ /n26.com/careers/

Recommend


More recommend