Fashion-driven architecture selects technology or style because it is popular, not because it fits the system’s needs, constraints, or operating reality. section 2.2
Test fashionable choices against the burdens they create:
- More services to operate, environments to govern, alerts to tune, skills to acquire, and ownership boundaries to coordinate. section 2.2
- Different scale, team structures, operational maturity, and budgets can make another organization’s architecture a poor model. section 2.2
- Prefer the less fashionable option when it offers better cost control, maintainability, observability, and fit. section 2.2
Microservices versus a modular monolith
Microservices may suit massive scale, independent team ownership, and mature platform capabilities. For smaller problems, infrastructure, coordination, testing, and observability costs may make a modular monolith the more responsible choice. section 2.2
Figure 2.3 Budget changes the architecture that is realistic.

Use the figure to connect budget pressure with the set of architectures an organization can realistically operate. section 2.2
