Planning & architecture

Explore Planning & architecture.

6 field notes

Architecture boundaries & dependencies

Dependency direction is not call direction

Planning & architecture / Architecture boundaries & dependencies01

Clean architecture

Point source dependencies toward policy.

Open field note

Swap edge technology, keep application behavior

Planning & architecture / Architecture boundaries & dependencies02

Hexagonal architecture

Keep application behavior behind technology-independent ports.

Open field note

Logical layers can share one deployment

Planning & architecture / Architecture boundaries & dependencies03

Layered architecture

Separate responsibilities with explicit dependency rules.

Open field note

Service decomposition

Independent releases introduce remote failure cases

Planning & architecture / Service decomposition04

Microservices

Release capability services independently.

Open field note

Internal contracts, shared release

Planning & architecture / Service decomposition05

Modular monolith

Keep module ownership inside one release unit.

Open field note

One release unit can contain many capabilities

Planning & architecture / Service decomposition06

Monolith

Release the server application as one unit.

Open field note