Breaking Change
Every breaking change except one produces an error somewhere. Redefining what a field means produces correct-looking numbers that disagree with last month’s.
-
-
Splitting the System Was the Easy Part: Cloud Native and Where Services End
Two services that deploy together and share a database are one system with a network call in the middle. The split added cost and removed nothing.
-
Conway’s Law
Copying another company’s service topology imports their communication structure, not their results. Their boundaries encode who talked to whom.
-
Modular Monolith
Modules that are only a folder convention are not boundaries. What makes it modular is that crossing a boundary the wrong way fails the build.
-
Cloud Native
The definition names loose coupling and five operational qualities. Containers and microservices appear in it as examples, and explicitly as a partial list.
-
ATAM
ATAM evaluates an architecture by turning quality goals into concrete scenarios and finding the decisions they hinge on: risks, sensitivity and tradeoff points.
-
C4 Model
The C4 model describes software at four zoom levels and keeps deployment separate, so structure and where it runs stay two distinct questions.
-
4+1 Architectural View Model
Kruchten’s 4+1 model describes a system through four views plus scenarios, keeping structure, concurrency, modules, and deployment as separate concerns.