# Two teams ship code on different schedules Canonical URL: Domain: Pipeline Design ยท Difficulty: medium ## Problem Two teams ship code on different schedules. The producer team ships a new schema version of the user_signup event next Monday; the consumer team that reads the topic will not deploy its update for another two weeks. During that two-week gap the consumer must keep reading old events that are still in flight on the topic, plus the new events the producer has started writing. The section names this exact scenario as the backward-compatibility case. Pick the compatibility mode by adding a schema registry node whose name states the compatibility setting the topic will enforce so that incompatible schemas are rejected at registration; the registry must sit between the producer and the Kafka topic so the check runs before the new schema can be published. ## Related - [All practice problems](https://datadriven.io/problems) - [Mock interview mode](https://datadriven.io/interview/two-teams-ship-code-on-different-schedules-the-producer-tea-318997ed) - [System Design Interview Questions](https://datadriven.io/data-engineering-system-design) - [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep) - [Daily Challenge](https://datadriven.io/daily) --- Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.