Part 3 of 8 · 2 min read
The inputs
Six inputs from the book, and one more.
FSA lists six things an architect should have in hand. A seventh row is added here.
| Input | What it means |
|---|---|
| The domain | The main aspects of the business, especially those that affect operations. No need to be an expert |
| Characteristics that affect structure | The "-ilities" needed (Level 0), found and ranked |
| Data architecture | Database and schema concerns, particularly if the system must work with an old or live data design |
| Organisational factors | Costs of a cloud vendor, plans for mergers, and similar |
| Process, teams and operations | Development process, link with operations, QA. If the team lacks mature agile practice, a style that relies on it will suffer |
| Domain and architecture isomorphism | Whether the shape of the problem matches the shape of a style |
| Team skills and tools (added here, not an FSA item) | What the team already knows and what tools are available |
Isomorphism means "same shape". FSA's examples: a problem that needs heavy customisation matches the microkernel style, because each customisation is a plug-in. A task with a very large number of discrete operations, such as genome analysis, fits the space-based style, which has many parallel processors. The reverse also holds. A domain with a lot of linked context is a poor match for a highly decoupled style. FSA's example is an insurance application with multi-page forms, each depending on the earlier pages. That is hard to model as microservices, and a less decoupled style such as service-based suits it better.
Domain and architecture isomorphism
Isomorphism here means that the shape of the problem matches the shape of the architecture style.
Example: a product where each customer needs different rules fits a plug-in style, since each customer's rules become one plug-in.
Check yourself: 1. Which input would tell you that a team cannot run many services yet? 2. What does isomorphism mean in plain words? 3. Why is a multi-page form that depends on earlier pages a poor match for microservices?