How to use Data Contracts for Long-Term Schema Management

https://is1-ssl.mzstatic.com/image/thumb/Podcasts211/v4/57/09/b6/5709b60f-7c03-a2b5-c522-6313d4257083/mza_18135812347693630014.jpg/600x600bb.jpg

Confluent Developer ft. Tim Berglund, Adi Polak & Viktor Gamov

Confluent

265 episodes

2 months ago

Hi, I'm Tim Berglund. It's been about four years since I've been podcasting at Confluent, and "Streaming Audio" has been on hiatus for a little more than two, but I've got great news: we are back! We're back with a new name, a new format, and new hosts. Welcome to the Confluent Developer Podcast, where we talk to software developers of all stripes about some of the most interesting problems they've solved in their career. I'll be joined by my co-hosts, Adi Polak and Viktor Gamov.&...

All content for Confluent Developer ft. Tim Berglund, Adi Polak & Viktor Gamov is the property of Confluent and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.

How to use Data Contracts for Long-Term Schema Management

Confluent Developer ft. Tim Berglund, Adi Polak & Viktor Gamov

57 minutes

2 years ago

How to use Data Contracts for Long-Term Schema Management

Have you ever struggled with managing data long term, especially as the schema changes over time? In order to manage and leverage data across an organization, it’s essential to have well-defined guidelines and standards in place around data quality, enforcement, and data transfer. To get started, Abraham Leal (Customer Success Technical Architect, Confluent) suggests that organizations associate their Apache Kafka® data with a data contract (schema). A data contract is an agreement between a ...