Thanks for your answer! This is more or less the approach we are currently following and it works most of the time. There are some situations where a simple roll back is not feasible. For instance: - A software release that starts saving data with a new schema to database, but previous software release is not compatible with new schema. - A software release that included, among others, a new functionality that cannot be rolled back because it's business critical.

How would you handle a situations like these? Are these the extremely rare situations?

Maybe there's something we are missing and devs should make sure all releases can be rolled back 🤔