Agility vs stability

How do you like your data?

Do you want it to be agile? So it can change at any moment, depending on the needs or wants of those producing the data? If a team decides it wants to model an object differently, with different IDs, they can do so. They are moving fast and breaking things.

Or do you want it to be stable? You’re building for the medium-to-long term and deploying your data-driven applications in front of your paying customers, who need to those applications to be dependable. You’ve got a long backlog and can’t waste your time rebuilding the same things over and over again. Your engineers are leaving because being on-call is a nightmare.

You can’t have both. Which would you choose?

P.S. I’ll be on a live panel Monday evening discussing “Data Contracts: The Next Frontier”. It’s 6pm GMT. Come join us!