Don't Panic — Software Architecture Fundamentals

Software architecture is the consequential structure of a system: the parts that matter, their relationships, and the reason those relationships were chosen. This is not a product diagram wearing a serious expression, nor a list of frameworks waiting to be declared modern. It is the part where a system admits that changing one thing may disturb another.

The job begins with an outcome, a constraint, and a quality attribute such as availability, security, performance, or modifiability. Those words are not decorations for a review meeting. They become a measurable scenario: a named stimulus happens, a particular path responds, and an agreed measure says whether the response was good enough. Without that measure, a favored architecture style is mostly a very organized hunch.

Then come the boundaries, which are determined to use the same word while answering different questions. A responsibility boundary says what work belongs together. A runtime boundary says what starts and fails together. A data boundary says who may change a fact and enforce its invariants. They can line up beautifully, which is pleasant, but they do not do so by default.

The surprise is that separation does not remove coordination. It gives coordination a name, a contract, and somewhere to fail in public. A network relationship needs a request or message shape, timeout, error behavior, compatibility rule, authentication, and recovery behavior. A shared database can tie apparently independent services together with a determination that deserves respect, if not applause.

Use the Intro when the vocabulary and the overall model need room to breathe. Use Slides when the relationships and trade-offs need a compact map. Use the Cheatsheet when deciding which boundary or style question to ask next. The practice reference turns those questions into a review technique, and the exercise asks you to make the structure, failure path, and evidence agree. Architecture decision records keep the consequential choice and its consequences from disappearing when the diagram acquires a successor.