dont you hate it when your database schema needs an update on a live system?

when youre working with a production system that has a lot of data and is actively being used, changing the database schema can be a nightmare. rolling back changes is often not an option. ive seen teams use techniques like blue-green deployments for schemas, but thats complex. whats your go-to strategy for safely evolving schemas without causing downtime or data corruption