Skip to main content

© 2026 Stephen Adei. All rights reserved. All content on this site is the intellectual property of Stephen Adei. See License for terms of use and attribution.

Architecture Decision Records (ADRs)

Overview

This directory contains Architecture Decision Records (ADRs) documenting key architectural decisions, their rationale, alternatives considered, and consequences. ADRs provide a historical record of why certain choices were made, enabling future maintainers to understand the context behind architectural decisions.

Extended context: Design Decisions Summary, Data Lake Architecture.


ADR Index

ADRTitleStatusDateSummary
ADR-001Parquet-only Format (not Iceberg/Delta)Accepted2026-01-30Use Parquet format without Iceberg/Delta for batch OLAP workload
ADR-002Year/Month Partitioning StrategyAccepted2026-01-30Partition by year/month for query optimization aligned with month-end reporting
ADR-003Serverless Architecture (Glue/Athena)Accepted2026-01-30Choose serverless over always-on compute for batch workload
ADR-004Quarantine + Condemned LayersAccepted2026-01-30Implement error handling layers for FinTech audit requirements
ADR-005Dual Pandas + PySpark ImplementationsAccepted2026-01-30Maintain both Pandas and PySpark implementations for different scale requirements
ADR-006run_id Isolation PatternAccepted2026-01-30Use run_id isolation for safe backfills and idempotent reruns
ADR-007Explicit S3 Lifecycle RulesAccepted2026-01-30Use explicit lifecycle rules instead of Intelligent-Tiering

ADR Status Definitions

  • Accepted: Decision has been made and implemented
  • Superseded: Decision has been replaced by a newer ADR
  • Deprecated: Decision is no longer applicable

See also

© 2026 Stephen AdeiCC BY 4.0