solution-architect
3 free lessons tagged solution-architect across Business. Each one is a short sequence of focused steps with narration and a five-question quiz at the end — take them in any order, no signup required.
Trade-offs, Decisions, and How to Break In
There is no best architecture, only trade-offs made for a context. This lesson covers the core of the job: analyzing trade-offs between quality attributes, the build-versus-buy decision and total cost of ownership, recording decisions with ADRs, communicating a design with the C4 model, and how a switcher grows into the role.
Requirements and the Quality Attributes That Decide Architecture
Most systems are shaped less by what they do than by how well they must do it. This lesson covers the requirements a solution architect must extract: functional versus non-functional, the quality attributes (the -ilities) captured by ISO 25010, why NFRs drive the architecture, and how to make vague quality demands testable.
What a Solution Architect Actually Does
A solution architect sits between a business problem and a technical solution, and is accountable for whether the solution fits. This lesson defines the role, separates it from enterprise and technical architects, explains why the job is about judgment and trade-offs rather than coding, and shows how engineers grow into it.