Every architecture starts with a question: what does this system need to do, and how well does it need to do it? Functional requirements describe the features and behaviour users see, while non-functional requirements describe qualities such as performance, availability, security, and maintainability. Those qualities are the ones that most strongly shape the architecture you choose.
You'll start by separating functional from non-functional requirements, then look at architecture characteristics, also known as quality attributes or the "-ilities", and how to identify which ones matter for a given system. From there you'll see how quality attribute scenarios make vague wishes testable, and how SLAs, SLOs, and SLIs turn reliability goals into numbers you can measure.
Next up is Architectural Styles, where you'll see how these quality goals guide the choice between a monolith, microservices, and event-driven designs.
Functional requirements describe what a system must do and non-functional requirements describe how well it must do it, explained with a simple everyday example.
Architecture characteristics, also called the "-ilities", non-functional requirements, or system quality attributes, and the qualities they define for an architecture.
A brief description of quality attributes and quality attribute scenarios, and how they relate to software architecture.
The definitions and differences between a service-level agreement, objective, and indicator, and how they turn availability and performance goals into measurable targets.