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:
Getting Started with Flyway and Version- Based Database Migration: thorben-janssen.com/flyway-ge...
Version-Based Database Migration with Liquibase - Getting Started: thorben-janssen.com/database-...
If you like this video, please give me your thumbs up and share it with your friends and co-workers.
Like my channel? Subscribe!
➜ bit.ly/2cUsid8
Join the free Member Library:
goo.gl/dtyIIC
Read the accompanying post: thorben-janssen.com/update-da...
Want to connect with me?
Blog: thorben-janssen.com/
Twitter: / thjanssen123
Facebook: / thoughtsonjava
Instagram: / thoughtsonjava
#DatabaseMigration #Hibernate #DatabaseUpdate
Негізгі бет Ғылым және технология Database Migration: Update your schema without a downtime
Пікірлер: 6