Forces are competing concerns or constraints that must be addressed when solving a problem in a particular context.
Forces are the concerns that a solution must address in a particular context. They can conflict, so a design may require prioritizing some over others. Making them explicit clarifies which issues matter for the decision. section 7.6.1
Performance versus understandability
Reactive code can improve performance while making code harder to understand. The context determines which concern takes priority. section 7.6.1
How Microservices Patterns, Second Edition covers it
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.
How it connects
Connects forces with patterns, resulting context, and related patterns.
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.
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.