If you embrace both structure and a defined path to change that structure, you get the best of all worlds. Database migrations and scheme changes should be the norm, not a feared last resort.
Otherwise you end up with equivalent logic littered throughout multiple application codebases sharing the same database.
Otherwise you end up with equivalent logic littered throughout multiple application codebases sharing the same database.