My Innovative Solution to Software Development: Versioned Database Migration
A good software project shall have a repeatable, quick, reliable database structure change process.
This is included in the “My Innovative Solution to Test Automation and Continuous Testing” series.
In an ideal world, architects design the database well so that it won’t change much during its development. However, as we know, the reality is very different, especially in agile projects (pretty much every one of them nowadays). You do need to alter your database tables’ structure, a lot.
Since 2007, I have observed that an important step was totally missing in many companies’ so-called CI processes: Database Migration. It seems all software teams are managing the database schema manually. Given the database schema needs to evolve frequently, wouldn’t that be a big risk?
Software Teams Need Versioned Database Migration
Many years ago, I watched a presentation by Scott Ambler, the co-author of “Refactoring Databases: Evolutionary Database Design” book…
