post
Metadata is product infrastructure, not documentation
A practical pattern for turning scattered technical knowledge into queryable metadata: stable identities, version history, clear ownership, and views people can actually use.
tag
#architecture
5 items · 5 feed items
feed
post
Why data contracts matter more than dashboards
Dashboards usually reveal a data problem after it has travelled through half the platform. Data contracts move the conversation upstream: clear schemas, ownership, compatibility rules, and a better way to change pipelines.
post
Architecture series, part 2: Kappa architecture, the reaction
Part 2 of a 2-post series. Kappa architecture is what you get when you ask 'what if we just did everything as a stream and replayed from the event log when we need to reprocess?' One pipeline, no diverged-codebase pain. Here's how it works, where it shines, and where it still bites.
post
Building a programmatic data-quality platform that teams actually adopt
Architectural pattern for a multi-tenant data-quality platform across many teams. Why centralising contracts beats centralising data, and how the SDK + control plane + fact/dim store pattern works regardless of which tools you reach for.
post
Architecture series, part 1: Lambda architecture, where it came from and why it hurt
Part 1 of a 2-post series on streaming-data architectures. Lambda architecture solved the right problem in 2014: how to combine batch correctness with stream-low-latency. The cost was running two pipelines for the same logic. Here's why it was right then, and why most teams shouldn't pick it now.