Advanced Software Architecture #trade-offs #CQRS #eventual-consistency #scaling

Trade-Off Communication

Gain: name the specific system attribute you improve (latency, throughput, availability, scalability dimension)
Cost: name the specific attribute you sacrifice or complexity you introduce
Constraint: state what consumers of the system must now tolerate or handle

5 exercises — practise the vocabulary architects use to frame trade-offs precisely: "we optimise for X at the cost of Y", CQRS framing, explaining eventual consistency across audience levels, caching trade-off statements, and horizontal vs. vertical scaling.

Trade-off communication quick reference

"We optimise for X at the cost of Y": names a deliberate trade-off — specific attributes, not vague "better/worse"
"We gain X at the cost of Y — callers must tolerate Z": full trade-off statement including consumer constraint
Eventual consistency (non-technical): "data propagates within a few seconds — you always get a response"
Horizontal scaling: add nodes; enabled by stateless, shared-nothing architecture
Vertical scaling: add CPU/RAM to one node; limited by hardware ceiling
Cache staleness window / TTL: the accepted maximum time between write and consistent read

Question 1 of