#release-engineering - February 2024 | Slack Archive

Here's one, for you release-engineering types.
What's the approach that most folks take these days for handling db migrations. Laravel, or whatever. Do folks tightly couple the migrations with the application, applying them at the time of app code deploy? I still see this frequently, and it seems aweful.
My answer is the same as always -- to manage the DB schema/queries/etc., as their own versioned products. This way if you know your app is going to need a new column you can make that change before the app is deployed. As you would do with any dependency. LMK, I'm interested in finding out what others see/do.