DE Architecture Decision Records

When to Use

Load this skill when the user needs to:

Choose between two or more data engineering technologies or approaches ("which tool should we use for X?")
Design the high-level architecture for a new data platform component ("how should we architect Y?")
Evaluate and score competing options ("we need to decide between A and B")
Write up or document a past decision for the team record ("document why we chose Z")
Understand the trade-offs of a specific DE architectural pattern
Communicate a technical decision to non-technical stakeholders or leadership
Manage the lifecycle of existing ADRs (supersede, deprecate, link to code)

Every Architecture Decision Record follows this template. Fill every section — leaving a section blank signals the analysis is incomplete.