Database Migration: Update your schema without a downtime

Updating a database schema is pretty easy if you can take your application offline. You shutdown the application, create a backup of the current database schema, perform all required update operations using tools like Flyway or Liquibase, restart the application and hope that everything works fine. But that changes if your customers don’t accept any downtime. Simple changes, like removing a column or renaming a table, suddenly require a multi-step migration process. The reason for that is that high-available systems make heavy use of redundancy.
In this video, I will show you how to update your database without a downtime. if you are new here and want to learn how to build incredible efficient persistence layers with JPA and Hibernate and all types of other Java persistence related stuff, start now by subscribing and clicking the bell, so you don't miss anything.

Links mentioned:

If you like this video, please give me your thumbs up and share it with your friends and co-workers.

Like my channel? Subscribe!

Join the free Member Library:

Want to connect with me?

#DatabaseMigration #Hibernate #DatabaseUpdate

[MuhammadBinZafar]

This was a great resource! I made notes of 8 pages. End-to-end informative, 💡insightful, and concise. Thorben Janssen is a knowledgeable person. Wish the best for you!

[lambdaboss]

Exactly the information I was looking for. Thank you.

[sebascarra]

Or, you can just forbid any updates or deletions, just creating and reading data. Of course, this means you would have to change your entire models paradigm entirely.

[eduardoaranda]

Would you use different git branches for each step ?