Part 1 of 7 · 1 min read
Why this page comes first
In this module you will
- Name the four parts of a software architecture and say why "it is microservices" is not a full description.
- Tell an architecture decision from a design principle and from a plain technology choice.
- Analyse a choice by listing its trade-offs, using the topic against queue example.
- Write a short architecture decision record with the five standard sections.
- Describe what is expected of an architect, and why architecture and design cannot be handed over a wall.
Levels 1 to 6 gave the building blocks: servers, databases, caches, queues and logs. This level is about the shapes a whole system can take and how to choose one. A shape is a choice with costs, so the first need is the vocabulary of decisions and trade-offs. The book used is "Fundamentals of Software Architecture" (FSA), chapters 1, 2 and 19. The numbers are made up to show the idea, unless the text names a book.