CSE Roadmap

Common tier · about 3 hours · 7 parts

Part 2 of 7 · 2 min read

More than a diagram

An architecture is the structure plus the qualities it must deliver, the decisions that shape it and the principles that guide it.

Think of a house. A floor plan shows rooms and doors. It does not say whether the house must survive floods, why the kitchen faces north, or that nobody may knock down a certain wall. Those facts matter as much as the plan.

FSA defines software architecture with four parts:

Part What it is Example
Structure The architecture style or styles the system uses Layered, microservices, microkernel
Architecture characteristics The "-ilities" the system must support Scalability, availability, deployability
Architecture decisions Rules for how the system is built Only the business and services layers may touch the database
Design principles Guidelines for how to build Prefer asynchronous messaging between services

Software architecture

Software architecture is the structure of a system together with the characteristics it must support, the decisions that constrain it and the design principles that guide it.

Example: "a layered web shop that must stay available at 99.9 percent, where only the service layer may call the database, and where teams prefer messaging between modules".

The book's warning: if an architect answers "it is a microservices architecture", only the structure has been described. The success criteria, the rules and the guidance are missing, and without them nobody can tell whether the architecture is right.

Architecture characteristic

An architecture characteristic (also called a quality attribute or "-ility") is a property of the system, apart from its features, that is needed for it to be a success. [Level 0, module 5 listed them.]

Example: a ticket site may need to handle a burst of 100,000 visitors when sales open. Scalability is the characteristic. The feature "buy a ticket" does not say it.

The characteristics define the success criteria and are mostly independent of what the system does. A bank and a game both need to be reliable, though they do different things.

Check yourself:

  • Which of the four parts is described by "must stay available during sales"?
  • Why is "we use microservices" an incomplete answer to "what is your architecture"?