[kapua-dev] Liquibase client integration strategies

[Henryk Konsek <hekonsek@xxxxxxxxx>]

Hi,

On today’s Kapua call we will discuss the best approach for Kapua Liquibase client execution.

So far our understanding is that the best approach to attack this problem will be to use self-contained Liquibase client per service, so in such scenario each service would be responsible for checking on startup if its schema has been applied yet or not.

The latter approach is promoted by Spring Boot. Here is the code [1] from Spring Boot responsible for pulling Liquibase Spring client [2] and Spring Boot configuration together.

As we don't want to become Spring-dependent, we should probably consider rewriting SpringLiquibase [2] client (but without Spring) in Kapua.

What do you think?

Cheers!

[1] https://github.com/spring-projects/spring-boot/blob/v1.4.3.RELEASE/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/liquibase/LiquibaseAutoConfiguration.java

[2] https://github.com/liquibase/liquibase/blob/master/liquibase-core/src/main/java/liquibase/integration/spring/SpringLiquibase.java

--

Henryk Konsek

https://linkedin.com/in/hekonsek