Architectural trade-offs
There are inherent trade-offs that must be made in any software architecture. Some architectural trade-offs are obvious, such as performance versus security or availability versus consistency, while others are quite subtle such as resiliency versus affordability. Jeremy Deane explores a number of architectural trade-offs and offers strategies for dealing with them.
| Talk Title | Architectural trade-offs |
| Speakers | Jeremy Deane (Foundation Medicine) |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | New York, New York |
| Date | February 26-28, 2018 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
The role of a technical lead or software architect is to design software that realizes the vision of the stakeholders. However, as the design evolves, conflicting requirements emerge that impact the candidate architecture. Resolving these conflicts often involves architectural trade-offs, such as granularity versus maintainability. In addition, with time-to-market pressures and having to do more with less, adopting a bloated architectural framework like TOGAF or using a time-consuming process like ATAM is not an option. Thus, it is essential to have a deep understanding of architectural trade-offs and know when to use lightweight resolution techniques. Jeremy Deane explores a number of architectural trade-offs and offers strategies for dealing with them.
