Forces
Forces are contextual pressures, competing concerns, or constraints that shape which solutions or system designs are feasible.
Software Architecture Decision-Making
An architectural force is a contextual pressure or constraint that shapes which system designs are feasible.
- How it is used
- Frames architecture as selecting viable designs under delivery, organizational, and operational pressure.
- How deep it goes
- Defines major forces and their trade-offs, then connects changing pressures to feedback and rebalancing.
- Examples
- Uses deadlines, budget limits, skill gaps, legacy contracts, fragile integrations, missing tests, and AI-assisted delivery as examples.
- What you can do after
- Evaluate/understand architectural options by making constraints, trade-offs, and long-term consequences explicit.
Read how Software Architecture Decision-Making explains forces →
Microservices Patterns, Second Edition
Forces are competing concerns or constraints that must be addressed when solving a problem in a particular context.
- How it is used
- Clarifies the concerns that a pattern must address in its specific problem context.
- How deep it goes
- Defines conflicting concerns and explains contextual prioritization, without prescribing a universal priority.
- Examples
- Contrasts reactive code’s performance with synchronous code’s relative understandability.
- What you can do after
- Evaluate competing concerns and prioritize them according to context.
Read how Microservices Patterns, Second Edition explains forces →
Related concepts
- model architectureuses · Model architecture is the structural arrangement of a computational model’s components, connections, and operations that determines how it processes inputs and produces outputs.
- patternpart of · A pattern is a reusable approach to solving a recurring problem within a particular context.
- team capabilityincludes · Team capability is the collective skills, knowledge, experience, and capacity a team can bring to its work.
- time-to-marketincludes · Time-to-market is the elapsed time from initiating an effort to making its resulting product, feature, service, or campaign available to its intended audience.
- architectural decisionuses · An architectural decision is a significant choice about the structure, behavior, interactions, or technical constraints of a software system.
- risk toleranceincludes · Risk tolerance is the degree and types of uncertainty or potential adverse outcomes that an individual or organization is willing to accept while pursuing objectives.
Questions about forces
What is forces?
Forces are contextual pressures, competing concerns, or constraints that shape which solutions or system designs are feasible.
Which Manning books explain forces?
Software Architecture Decision-Making and Microservices Patterns, Second Edition.
What kinds of forces are there?
Kinds of forces include team capability, time-to-market and risk tolerance.
What is forces part of?
Forces is part of pattern. A pattern is a reusable approach to solving a recurring problem within a particular context.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

