Part 3 of 7 · 2 min read
Decisions and principles
A decision is a rule that can be checked. A principle is advice that leaves room for judgement.
Think of a school. "No running in the corridor" is a rule. "Be kind to younger pupils" is guidance. A teacher can check the first. The second depends on the moment.
FSA separates the two.
Architecture decision
An architecture decision is a rule for how the system is built. It is a constraint that teams must follow.
Example: "Only the business and service layers may access the database. The presentation layer must never call it directly."
Design principle
A design principle is a guideline, not a hard rule. It names the preferred way and lets developers choose another when the case needs it.
Example: "Use asynchronous messaging between services to improve performance." A developer may still use REST or gRPC where a direct answer is needed.
A rule cannot cover every case, which is why principles exist. Sometimes a rule cannot be followed in one place. The book describes a variance: a formal request to break a decision for a stated reason. An architecture review board or a chief architect weighs the justification and the trade-offs and approves or denies it.
The decision about the database in the example has a reason, which the book gives: to control change. If the presentation layer never calls the database, the database can change without breaking the user interface. A developer who bypasses the rule for speed loses that protection. This is why the architect must check that teams follow the decisions.
Guide, do not choose for the team. The book advises that an architect should guide technology choices rather than make them. "Use a reactive web framework" guides the team, which then picks among several. "Use React" makes the choice for them. The exception: when a specific technology is needed to protect a characteristic such as scalability, naming it is still an architecture decision.
A worked example (made up). A shop has these statements:
| Statement | Decision, principle or technology choice? |
|---|---|
| Services must not read each other's databases | Decision (a rule) |
| Prefer events to direct calls where an answer is not needed at once | Principle (a guideline) |
| The orders table lives in PostgreSQL 16 | Technology choice (not architectural unless a characteristic depends on it) |
| Every public endpoint must answer within 300 milliseconds at the 99th percentile | Decision with a measurable limit |
Check yourself:
- What does a variance do?
- Why is "use React" a poor architecture decision, according to FSA?