Cross-Cutting Tensions¶

These tensions appear across multiple domains, indicating fundamental trade-offs that cannot be eliminated - only managed.

Consistency vs. Availability¶

Appears in:

• Distributed Fundamentals
• Data Modeling & Persistence
• Distributed Patterns

Flexibility vs. Simplicity¶

Appears in:

• API Design
• Software Design

Generality vs. Efficiency¶

Appears in:

• Algorithm Patterns
• Algorithmic Thinking

Inheritance vs. Composition¶

Appears in:

• Software Design
• Programming Paradigms

Latency vs. Throughput¶

Appears in:

• Storage & I/O Foundations
• Performance Optimization

Safety vs. Liveness¶

Appears in:

• Distributed Fundamentals
• Concurrency & Parallelism

Security vs. Performance¶

Appears in:

• Security Patterns
• Networking Foundations

Simplicity vs. Capability¶

Appears in:

• Software Architecture
• Data Structures

Simplicity vs. Performance¶

Appears in:

• Performance Optimization
• Networking Foundations

Time vs. Space¶

Appears in:

• Algorithm Patterns
• Algorithmic Thinking

About Tensions¶

Every domain in this compendium begins with its fundamental tensions. These represent the core trade-offs engineers face - situations where improving one dimension inevitably affects another.

Understanding tensions is more valuable than memorizing solutions because:

1. They're timeless: The tension between consistency and availability will exist as long as there are distributed systems
2. They transfer: The same tension may appear in different forms across domains
3. They frame decisions: Once you recognize the tension, you can make informed trade-offs rather than cargo-culting solutions

When you encounter a new domain or technology, look for its fundamental tensions. They'll tell you what problems it's actually solving.