Explore
Here you can see the 12 Areas of software architecture in three chapters – from foundation to system design to operation. You explain everything to yourself in a continuous example.
Our case study
So that architecture does not remain abstract, you work everywhere on the same fictional shop. Customers order products there, a team develops and operates it. Each building block shows its theme exactly at this shop.
Often with: Order B-1042 over Two cups.
Shop application · a modular monolith
Entrusted with the order
Shared
Your learning path
The learning path leads you building block by building block through all three chapters, always using the example of the online shop.
Chapter I · 4 Areas
Here you will find the terms, quality goals and business limits for your design.
26 Building blocksQuestion at the shop: Which modules make up the shop, and where does the payment provider begin?
Here you get the overview: structure, interaction and decisions in the software architecture.
7 Building blocks
Open areaQuestion at the shop: How quickly must the shop respond to a payment request, and how do you measure that?
Here you will find the goals and guidelines against which you align your draft.
6 Building blocks
Open areaQuestion at the shop: What should the invoicing module know about an order, and what should stay hidden?
These principles help you to distribute tasks clearly and to control dependencies in a targeted manner.
6 Building blocks
Open areaQuestion at the shop: Do order and invoice mean the same thing when both speak of an “amount”?
Learn how domain language, models and responsibilities shape your design.
7 Building blocks
Open areaChapter II · 4 Areas
Here you will learn how structures, data and communication together form a system.
32 Building blocksQuestion at the shop: Does the shop stay a modular monolith, or does shipping become a separate service?
Here you will find architectural styles and patterns with their benefits, their prerequisites and their consequences.
8 Building blocks
Open areaQuestion at the shop: Who owns the order tables when all modules share a database?
Here you will find approaches for data ownership, storage and reliable state changes.
9 Building blocks
Open areaQuestion at the shop: Must checkout wait until the invoice PDF is ready?
Here you will learn how system parts exchange data and work together reliably.
9 Building blocks
Open areaQuestion at the shop: What happens if the connection to the payment provider drops after sending a request?
Here you will find the basics for distributed states, networks and handling partial failures.
6 Building blocks
Open areaChapter III · 4 Areas
Here you will find building blocks for operation, security, further development and documentation.
30 Building blocksQuestion at the shop: What does the shop do if the payment provider has not responded after one second?
Here you will find building blocks for stable runtime, controlled releases and the diagnosis of faults.
10 Building blocks
Open areaQuestion at the shop: May a shipping carrier change the status of any order?
Here you will learn how to build trust limits, accesses and protections into your design.
7 Building blocks
Open areaQuestion at the shop: What does it cost when the shipping module reads order tables directly?
Here you will find procedures with which you test architecture and develop it step by step.
7 Building blocks
Open areaQuestion at the shop: How does the team record why the shop remains a modular monolith?
Here you will find formats for comprehensible architectural images and comprehensible decisions.
6 Building blocks
Open area