Mastering Solutions: Unraveling the Role of Solution Architects
summary
Defines Solution Architect as the end-to-end integrator who must stay technical (code reviews, PR discipline on GitHub), enforce ADR: context / decision / rationale / alternatives / consequences and produce SADs that name NFRs. Chooses protocols (REST vs ProtoBuf vs Kafka streaming), designs for metrics traces logs observability, configures Kubernetes across fault domains and decides active‑active vs active‑passive. Translates business criticality into availability targets (example: two and a half nines = ~10 hours/year), drives POCs and documents exceptions so teams can execute without asking.
AI-written summary · about
chapters (8)
- 0:00Introduction to solution architects
- 7:25Tactical vs strategic focus
- 12:40Solution architect role and integrations
- 21:09Bridging business and technical teams
- 27:47Day-to-day responsibilities
- 37:23Stability and availability focus
- 48:42Disaster recovery and resilience
- 56:01Summary and key takeaways
related talks
25mFrom Requirements to Reality: How Solutions Architects Think, Build & Decide
45mArchitecture and the Architect AD2022
36mWho Is This So-Called Architect?
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
45mTeam and Software: Making an Impact as an Architect
14mthe growing role of software architects
59mHow to Think Like an Architect
43mApplying architectural principles, processes, and tools