Part 6 of 7 · 3 min read
What an architect does
The role is a set of expectations, not a title.
What an architect does
Think of a ship's navigator. The navigator does not row, but knows the engine, the weather and the cargo. The navigator also checks the crew keep to the course.
FSA lists eight expectations, whatever the title:
- Make architecture decisions (guide, do not dictate technology).
- Continually analyse the architecture. This is called architecture vitality: how well an architecture defined three or more years ago still fits business and technology. Neglect leads to structural decay, where code changes quietly damage characteristics such as performance or availability. Slow testing and release also limit agility.
- Keep current with trends. Architecture decisions last and are costly to undo.
- Ensure compliance with decisions, for example with automated fitness functions.
- Have diverse exposure and experience.
- Know the business domain.
- Have interpersonal skills: teamwork, facilitation, leadership.
- Understand and navigate politics. The book's example: an architect who locks a shared CRM database behind one application forces every other team to call it over a network. Almost every architecture decision is challenged.
Breadth over depth. Developers build depth in what they use daily. The book argues an architect gains more from breadth: knowing the pros and cons of ten caching products beats being an expert in one. It describes a knowledge pyramid of what you know, what you know you do not know, and what you do not know you do not know. Breadth enlarges the middle layer, so more solutions can be seen. It warns against the Frozen Caveman anti-pattern, where an architect keeps raising one old fear, like "what if we lose Italy?", in every design. Risk should be realistic.
Architecture and design work together. The old model has architects drawing structures and handing them to developers who write the code, with arrows going one way. The book says this is why architecture often fails: decisions never arrive, and changes made by teams never come back. Architect and developers should be one virtual team with two-way communication. The architecture changes in every iteration. Where does architecture end and design begin? It does not. Both are parts of one cycle.
A worked example (made up). A team's p99 latency target is 300 ms. A fitness function runs nightly. In month 1, p99 is 180 ms. In month 6 it is 290 ms. No one broke the rule on one day. Each change added a little. The check shows the decay early, when the architect can still react.
Interview angle
Answer in your head first, then open it.
What is software architecture?
Structure, characteristics, decisions and principles, not only a diagram.
What is a trade-off? Give one.
An option that gains one quality and loses another, such as topic extensibility against queue security and scaling.
How do you record a decision?
A short ADR with title, status, context, decision, consequences and a compliance check.
What does an architect do besides draw boxes?
Decide, check compliance, keep the architecture current, and work with the developers.
What is your answer to "which is better, REST or messaging?"
It depends. State the factors, then choose for the case.
Check yourself:
- What is structural decay, and how can it be spotted early?
- Why does FSA say architecture and design are one cycle?
Words you will meet
| Word | Plain meaning |
|---|---|
| Software architecture | Structure, characteristics, decisions and principles of a system |
| Architecture style | A named kind of structure, such as layered or microservices |
| Architecture characteristic | A quality the system must have, beyond its features |
| Architecture decision | A rule that constrains how the system is built |
| Design principle | A guideline that leaves room for judgement |
| Variance | An approved exception to a decision |
| Trade-off | Gaining one quality by giving up another |
| ADR | A short record of one architecture decision |
| Fitness function | An automatic check that a characteristic still holds |
| Architecture vitality | How well an old architecture still fits |
| Structural decay | Slow damage to the architecture from many small changes |
| Frozen Caveman | An architect who keeps raising one old fear |