The Consumer-Defined Data Contract - by Chad Sanderson

dataproducts.substack.com · 2,431 words · saved by 1 readers

Note from Chad: 👋 Hi folks, thanks for reading my newsletter! My name is Chad Sanderson, and I write about data products, data contracts, data modeling, and the future of data engineering and data architecture. I’ve been hard at work building Gable these last few months, but today we’re talking about the data contracts and some recommendations to super-charge adoption, so strap in. As always, I‘d love a follow and share if you find it valuable. While data contracts are not new, our modern federated implementation leveraging schema registries and CI/CD checks has much less organizational overhead than hand-written data-SLA documents. However, despite being excited that teams are beginning to adopt the concept en masse, I have been getting the sinking feeling that somewhere along the way a message was lost: “Producer-defined data contracts do not work.” Or rather, it’s less that they don’t work, and more that what is required for a successful producer-defined data contract implementatio

The Consumer-Defined Data Contract Why Producer-Centric Contracts (Can) Fail Chad Sanderson Dec 04, 2023 32 1 1 Share Note from Chad : 👋 Hi folks, thanks for reading my newsletter! My name is Chad Sanderson, and I write about data products, data contracts, data modeling, and the future of data engineering and data architecture. I’ve been hard at work building Gable these last few months, but today we’re talking about the data contracts and some recommendations to super-charge adoption, so strap in. As always, I‘d love a follow and share if you find it valuable. While data contracts are not ne

The Consumer-Defined Data Contract - by Chad Sanderson

related reading