Data Architecture
20 posts filed under Data Architecture.
Idempotency In Orchestration Failures
Your pipeline failed at 3am. The on-call engineer is now paid to clean up duplicates.
Read →Conway's Law Pipeline Silos
Two teams sitting in different Slack channels build two pipelines that compute the same metric.
Read →Contract-First Data For Cross-Team Handoffs
Most cross-team data fights are caused by an undocumented assumption upstream.
Read →Orchestration Tool Audit For Small Data Teams
Two-engineer data teams keep picking Airflow because it's "industry standard." Six months in, half the DAGs are commented out.
Read →Semantic Layer Is A Consistency Tool, Not A Speed Tool
A semantic layer is a consistency tool. Most teams buy it for speed and end up disappointed.
Read →Software Modernization Is Not Architectural Modernization
Software modernization and architectural modernization are different problems with different fixes.
Read →The Data Product Canvas (One-Page Definition)
An empty "consumers" field is the signal to deprecate the asset. Most teams ignore it.
Read →Data Platform Maturity Model (5 Stages)
Your data platform is at stage 2. You're copying stage 5 patterns. That's why it's breaking.
Read →When You Actually Need a Semantic Layer
Most teams buy a semantic layer the way they buy a data warehouse. Tool first, problem retrofitted.
Read →Building data platforms for technology instead of teams
The data platform nobody asked for is the data platform nobody uses.
Read →