A technology-oriented architectural style organizes a monolith’s domain architecture around technical responsibilities rather than business-domain concepts. This can scatter related subdomain code across layers, weakening cohesion and increasing design-time and build-time coupling. section 6.2 section 6.2.1
In a traditional layered monolith, technical concerns define the layers:
- Web holds user-interface or API logic. section 6.2.1
- Domain holds business logic. section 6.2.1
- Persistence holds database-access or infrastructure logic. section 6.2.1
FTGO layered monolith
Consumers, orders, and notifications span the technical layers: repositories sit in persistence, entities in domain, and controllers in web. The resulting structure can mismatch the subdomains and the teams developing them. section 6.2.1
Figure 6.7 In a technology-oriented layered architecture, the code for each subdomain is scattered across the technical layers. As a result, there’s a mismatch between the application architecture and the subdomains and the teams that develop them.
Shows subdomain code scattered across technical layers and the resulting mismatch with subdomains and teams. section 6.2.1
