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.
Jeremy Deane is chief architect at Foundation Medicine. Jeremy has over 22 years of software engineering experience in leadership positions. His expertise includes enterprise application integration, web application architecture, and software process improvement. He is also an accomplished conference speaker and technical author.
Comments on this page are now closed.
For exhibition and sponsorship opportunities, email SAconf@oreilly.com
For information on trade opportunities with O'Reilly conferences, email partners@oreilly.com
View a complete list of O'Reilly Software Architecture contacts
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • confreg@oreilly.com
Comments
The presentation is available online:
https://prezi.com/zgt7vz0q1oyy/architectural-trade-offs
Hi Jeremy,
thanks for sharing your knowledge during the conference. I attended this session and found it useful. Will you be posting your slides to be used as reference later?
Thanks in advance for posting,
Ruben