Portfolio ↗

Terminology

2185 terms, tools, patterns and metrics an architect is expected to use precisely. Each one gets a short explanation of what it is, and — where it matters — what it is commonly confused with. Search filters as you type; the column headers sort.

All areas2185 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture89 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture81 Cost Architecture & FinOps66 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization66 AI-Era Architecture69 Software Architecture & Engineering71 Architecture Patterns71 Architecture Decision-Making63 The Architect's Meta-Skills61 Delivery & Release Engineering66 Platform Engineering & Developer Experience70 Testing & Quality Architecture66 Data Platform Architecture64 Streaming & Real-Time Data69 Data Governance & Semantics69 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk64
Kind Any concept785 practice729 pattern362 metric125 case-study77 tool62 protocol45

5 terms shown.

Term Kind Topic What it is
Compensating Transaction pattern Sagas & Compensation A business operation that semantically undoes a previously committed step — not a rollback, because the original effect was visible and may not be fully reversible.
Compensation Impossibility Irreversible Step, Uncompensatable Action concept Sagas & Compensation The recognition that some saga steps have no true compensating action, and the design rule that follows - order steps by reversibility and gate the irreversible ones.
Outbox Pattern Transactional Outbox pattern Sagas & Compensation Writing a message to a table in the same database transaction as the state change, then publishing it asynchronously, so the two cannot diverge.
Pivot Transaction concept Sagas & Compensation The step in a saga after which the transaction can no longer be cancelled — everything before it is compensatable, everything after it is retriable until it succeeds.
Saga Orchestrator pattern Sagas & Compensation A component that explicitly drives a saga's steps and compensations, holding the flow in one place rather than distributing it across event subscriptions.