Summary of "Good Enough" Architecture • Stefan Tilkov • GOTO 2019

00:00:00 - 00:40:00

In the video, Stefan Tilkov discusses the importance of architecture and how it should be pragmatic and allow for evolution. He provides examples of different architectures and discusses the benefits and drawbacks of each.

• 00:00:00 In this video, Stefan Tilkov discusses how architecture can be too sophisticated or not sophisticated enough, and how this can lead to design problems. He also discusses two definitions for architecture, and how it can be a property of a system. He argues that a good architecture is something that is important to the people involved, and that it is not just a design activity that is completed at the beginning.
• 00:05:00 The video discusses the importance of architecture, and how it must take into account the quality attributes that a project or user cares about. It provides an example of a project that went wrong because the architecture was not customizable enough for the client's needs.
• 00:10:00 The video discusses how a company's architecture can be ruined by the addition of multiple teams and how a generic order service can become a problem.
• 00:15:00 The video discusses how a monolithic application was modularized and how this made it easier to refactor. It also discusses how a development process was created that lays out how the year is structured.
• 00:20:00 The video discusses the benefits and drawbacks of different architectures, including good enough, freestyle, and self-contained systems. It argues that a system with multiple, self-contained teams is the strongest form of isolation possible.
• 00:25:00 The video discusses the benefits and drawbacks of having an architecture that is "good enough." It argues that a centralized front end team will result in a bottleneck in the runtime or development architecture, and that a loosely coupled architecture is only achievable with strict rules. The video gives the example of a financial service provider that successfully built a long tail market using a small number of developers who were very familiar with the business.
• 00:30:00 The video discusses how a company decided to move away from a proprietary system and towards an open source solution. They explain that this was a difficult process, as they had to manage the entropy created by the evolution of the system.
• 00:35:00 The video discusses the importance of architecture, how it should be pragmatic, and how it should evolve. It provides an example of an architecture where different adapters are used for different systems.
• 00:40:00 The speaker discusses the yakhni principle, or the idea that it is okay to take risks in order to avoid having to do something later that may be more difficult. The speaker argues that architecture should be designed in a way that allows for evolution, so that it can be changed without causing disruption.