explain-system-tradeoffs

To analyze distributed system tradeoffs, you examine code, configuration, and architecture artifacts to identify system priorities and sacrifices. This process reveals what your architecture optimizes for and what potential risks it introduces across six key axes.

The key axes for evaluating system design decisions are Consistency vs. Availability, Latency vs. Throughput, Data Distribution, Transaction Boundaries, Resilience, and Observability/Security/Cost. Reviewing these axes reveals the specific tradeoffs your distributed systems make.

You audit a new microservice for reliability and performance risks by analyzing its design decisions against organizational standards. This evidence-based analysis identifies explicit and implicit tradeoffs, highlighting potential production impacts before deployment.

Yes, you can focus the system design audit on a single tradeoff axis like latency or consistency. The analysis supports both single-axis focus and comprehensive multi-agent parallel analysis for deep architectural audits across all six axes.

Tiered evidence in architecture tradeoff analysis is a classification system using tiers A, B, and C to rank the confidence of findings. It structures detailed reporting by evaluating code, configuration, and architecture artifacts to identify system sacrifices and risks.