An experience with Contract-Driven Development

Carles Climent
Feb 1, 2018 · 6 min read

A bit of background

How did we do (and are still doing)?

1. We divided the new feature in two subsystems (provider/consumer)

Architecture of the new feature

2. We defined a contract between the two subsystems

3. We broke each subsystem in tasks that could (kind of) be developed independently

4. We are feeding the consumer with hardcoded fake input

The writer is fed with fake data

5. We are programming, reviewing and testing each subsystem independently and in parallel

The system produces two documents with different purposes

6. Once ready, we’ll remove the hardcoded parts and we’ll connect both subsystems

Final thoughts

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade