liveBook · Manning

Forces

As explained in Microservices Patterns, Second Edition

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.

Also explained in

Compare how 2 books explain forces →

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.