Scaling out architectural decision making
In the fast-moving startup world, there's often not a lot of time to think about architecture. N26 wanted to ensure that it not only delivered fast but also delivered a quality product. Patrick Kua explores how the company scaled out architectural decision making as it grew very rapidly (in both customers and engineers).
| Talk Title | Scaling out architectural decision making |
| Speakers | Patrick Kua (N26) |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | Berlin, Germany |
| Date | November 5-7, 2019 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
In the fast-moving startup world, there’s often not a lot of time to think about architecture. N26 has a mission of building a bank the world loves to use and wants to ensure that it not only delivers fast, it also delivers a quality product. Patrick Kua explores how the company scaled out architectural decision making as it grew very rapidly (in both customers and engineers). Patrick outlines how decisions were made in the early phase of the company, the upsides and downsides to the early decision-making processes, and how the engineering organization changed in a period of 18 months and the impact that had on decision making. He also highlights a number of practices (request for comments (RFCs), architecture guild and working groups, and engineering principles) that have helped the company scale. You’ll learn what worked well and what didn’t work well for N26. Join in, especially if you’re part of an agile company trying to bring a more explicit focus to architectural thinking and trade-offs, particularly if your company is growing or is already larger than a couple of teams.
