# Canary Releases with SpringBoot

**URL:** <https://forum.flowable.org/t/canary-releases-with-springboot/7822>\
**Category:** Flowable Engine\
**Created:** [May 5, 2021, 4:53am UTC](https://forum.flowable.org/t/canary-releases-with-springboot/7822 "2021-05-05T04:53:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tannth](https://avatars.discourse-cdn.com/v4/letter/t/b3f665/32.png) [@tannth](https://forum.flowable.org/u/tannth)\
**Post date:** [May 5, 2021, 4:53am UTC](https://forum.flowable.org/t/canary-releases-with-springboot/7822/1 "2021-05-05T04:53:44Z")

</div>

Hi everyone,

Currently, we want to apply canary releases/ blue-green to CICD. I have a question about the database.

So Should we have a database for each engine/version?

For example:

The production environment is running version 1 then when have an alpha/beta version 2 which need to be running in the Production environment.

In my view, it’s ok for all if they are running in the flowable-engine-version like 6.6.0. But It will have a problem if they are running in different flowable-engine-version like the first one is 6.6.0, the second one is 6.7.0

Let give me an advice for this case. How we implement it in the real world?

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [May 12, 2021, 9:39am UTC](https://forum.flowable.org/t/canary-releases-with-springboot/7822/2 "2021-05-12T09:39:18Z")

</div>

If you migrate the relational database schema to the next version, there is a chance that the instance running the old engine version won’t work correctly anymore (e.g. when a column is removed). We typically avoid these type of changes, but it does happen (infrequently).