Summary : 

Currently we use liquibase to create our db schema and load the data/models in our datastore.

We intend to move away from liquibase due to some outstanding issues in it ( decision is already made )

Below are the sequence of events which happened.

• Initial version of liquibase was unable to retry when there are some distruption while it is trying to run the scripts.
• So we introduced a new mechanism where it was decided to use the post-upgrade and post-install hook to run the liquibase changes as part of it ( and dont create the schema as part of the application startup )
• But our new solution which is based on Loading the models based on Spring Application Events needs the database and schema been setup as part of the application startup which contradicts the solution which was introduced in the step above.

Now it is been agreed to investigate if we can remove the workaround solution ( as liquibase version got upgraded from the time that solution was introduced ) and check if we still see that issue. 
We see that updated liquibase version has the capabilities to retry during any disruption during schema creation.

Contact : csaba.eder emolger  for any updates.