Successfully reported this slideshow.

Scaling Architecture Decision Making (Trendyol Istanbul Meetup Jan 2020

1

Share

1 of 53
1 of 53

Scaling Architecture Decision Making (Trendyol Istanbul Meetup Jan 2020

1

Share

Download to read offline

In the fast moving startup world, there’s often not a lot time to think about architecture. As I grew N26 Tech almost 8x to 370 people in just over two years, I wanted to make sure we made good technical decisions and not just grow chaotically.

This talk explores how we introduced a number of practices how to decentralise and scale out architectural decision making.

In the fast moving startup world, there’s often not a lot time to think about architecture. As I grew N26 Tech almost 8x to 370 people in just over two years, I wanted to make sure we made good technical decisions and not just grow chaotically.

This talk explores how we introduced a number of practices how to decentralise and scale out architectural decision making.

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Scaling Architecture Decision Making (Trendyol Istanbul Meetup Jan 2020

  1. 1. @patkua Scaling Architecture Decision Making
  2. 2. #Architect #Developer #Coach #Leader #CTO #Life-long learner #Author #Speaker ~20 years experience Agile Software Development Organisational Change Systems Thinking Leadership Development @patkua
  3. 3. thekua.io/twtl thekua.io/retrobookthekua.io/evolarch @patkua
  4. 4. @patkua Course: Tech Lead Skills for Developers http://patkua.com/tlcourse @patkua
  5. 5. @patkua Level Up A curated newsletter for leaders in tech http://levelup.patkua.com @patkua
  6. 6. @patkua What did we learn? What did we do? Why scale decision making? @patkua
  7. 7. @patkua Why scale decision making? @patkua
  8. 8. @patkua
  9. 9. @patkua The context: Hypergrowth
  10. 10. @patkua
  11. 11. @patkua
  12. 12. @patkua Berlin Barcelona New York
  13. 13. @patkua Hypergrowth feels like you’re building the rocket as its flying “
  14. 14. @patkua
  15. 15. @patkua
  16. 16. @patkua Decisions
  17. 17. @patkua Decisions Design Architecture Easier to change Harder to change
  18. 18. @patkua Decisions Easier to change Harder to change BE <-> FE error standard Sync versus Async Standard “across” services Code layout within a service Method/function design Library
  19. 19. @patkua Decisions Decision Quality Buy-in Time
  20. 20. @patkua Decisions Fast AND good
  21. 21. @patkua Decisions How we used to make decisions…
  22. 22. @patkua Pain Points Meetings Information Locations Visibility
  23. 23. @patkua What did we do? Why scale decision making? @patkua
  24. 24. @patkua RFCs Working Groups Architecture Guild Practices
  25. 25. @patkua equest or omments R F C
  26. 26. @patkua RFCs
  27. 27. @patkua RFCs Introduced Organic adoption Confusion
  28. 28. @patkua Refactoring RFCs
  29. 29. @patkua RFCs Refactoring
  30. 30. @patkua Refactoring RFCs
  31. 31. @patkua ? RFCs
  32. 32. @patkua 83 RFCs
  33. 33. @patkua RFCs Working Groups Architecture Guild Practices
  34. 34. @patkua Working Groups
  35. 35. @patkua Working Groups
  36. 36. @patkua Design by CommitteeNO Informed Consulted Speed Working Groups
  37. 37. @patkua Listening for pain points Often about gaps Many perspectives Multiplier Working Groups
  38. 38. @patkua Example: Error Handling Working Groups
  39. 39. @patkua Example: Error Handling iOS Android Web Internal Service A Service B Service C Service D Working Groups
  40. 40. @patkua Example: Error Handling JSON? Structure What details? Already translated? Working Groups
  41. 41. @patkua 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
  42. 42. @patkua RFCs Working Groups Architecture Guild Practices
  43. 43. @patkua Architecture Guild
  44. 44. @patkua Architecture Guild What? - Representatives across the entire tech - Entire company wide cross cutting topics - Decision making authority
  45. 45. @patkua Who? iOS Android Web Security Data Internal Tools SRE BE Segment Location (BCN, NYC) QE Staff Engineers Architecture Guild
  46. 46. @patkua Example: Updating Tech Radar Architecture Guild
  47. 47. @patkua Example: Security Scanning in CD Pipe Architecture Guild
  48. 48. @patkua What did we learn? What did we do? Why scale decision making? @patkua
  49. 49. @patkua Learnings
  50. 50. @patkua Pain Points Meetings Information Locations Visibility Learnings
  51. 51. @patkua Learnings Listen Observe Refactor
  52. 52. @patkua Learnings Listen Observe Refactor Iterate
  53. 53. @patkua Scaling Architecture Decision Making @patkua Questions?

×