liveBook · Manning

Fashion-driven architecture

As explained in Software Architecture Decision-Making

Fashion-driven architecture is an architectural approach selected primarily because a technology or style is popular rather than because it addresses the system's actual needs.

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

How Software Architecture Decision-Making covers it

How deep it goes
Compares architectural consequences and contextual fit, but stops short of implementation guidance or a formal decision procedure.
Examples
Contrasts serverless with a virtual machine and microservices with a modular monolith under different scale and budget conditions.
What it assumes
Assumes familiarity with architectural styles and operations while teaching readers to question technology-led requirements.
What you can do after
Evaluate architectural fashion against infrastructure, coordination, testing, observability, ownership, and budget costs.
How it connects
Connects fashion-driven architecture with microservices, event streaming, Kubernetes, serverless computing, modular monoliths, and distributed systems.

This explainer was generated by Manning's knowledge graph from the text of Software Architecture Decision-Making. The section links point to the parts of the book it draws on.