liveBook · Manning

Architecture advice process

As explained in Microservices Patterns, Second Edition

The architecture advice process is a decision-making practice in which a decision-maker seeks input from everyone affected by an architectural decision and from experts in its subject area.

The architecture advice process lets anyone make and communicate an architectural decision, provided they first seek input from everyone affected and from experts in the decision’s area. section 3.4.2

Those consulted weigh in on candidate solutions and trade-offs. This helps decisions reflect their effects on teams while giving teams broader organizational context. section 3.4.2

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines who to consult and what input to seek, without detailing a step-by-step process.
What you can do after
Apply the practice by consulting affected people and subject-area experts before communicating an architectural decision.
How it connects
Connects decentralized decision-making with microservice architecture decisions at service and application levels.

Also explained in

Compare how 2 books explain architecture advice process →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.