# Custom history database

**URL:** <https://forum.flowable.org/t/custom-history-database/611>\
**Category:** Flowable Engine\
**Created:** [May 31, 2017, 9:08am UTC](https://forum.flowable.org/t/custom-history-database/611 "2017-05-31T09:08:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ganil.89](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/ganil.89/32/520_2.png) [@ganil.89](https://forum.flowable.org/u/ganil.89)\
**Post date:** [May 31, 2017, 9:08am UTC](https://forum.flowable.org/t/custom-history-database/611/1 "2017-05-31T09:08:23Z")

</div>

Hi,

In my project we are using flowable and there is a requirement such that we want to store history details in separate database instead of storing in database where engine is running. For example, a process instance started and completed, now these details will be moved to history tables of same database, but I want to move to another database. It means I will maintain a different database for runtime and history.  
Is this possible ??  
I searched for solution in flowable document and it does not contain this information. So could you please tell me how to achieve this in flowable if feature exist.

---

<div class="post-metadata">

**Author:** ![tijs](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tijs](https://forum.flowable.org/u/tijs)\
**Post date:** [May 31, 2017, 12:28pm UTC](https://forum.flowable.org/t/custom-history-database/611/2 "2017-05-31T12:28:26Z")

</div>

Hi,

With the next release of Flowable 6.1.0 we will have an async history option that will allow you to do exactly this. You will be able to store the historic information in any other data source by implementing an interface that will be invoked with different types of historic information.

But also in the current implementation this is possible by using event listeners:

[http://www.flowable.org/docs/userguide/index.html#eventDispatcher](http://www.flowable.org/docs/userguide/index.html#eventDispatcher)

You can register for certain event types and write the event data to a different database.

Best regards,

Tijs

---

<div class="post-metadata">

**Author:** ![ganil.89](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/ganil.89/32/520_2.png) [@ganil.89](https://forum.flowable.org/u/ganil.89)\
**Post date:** [June 1, 2017, 4:45am UTC](https://forum.flowable.org/t/custom-history-database/611/3 "2017-06-01T04:45:07Z")

</div>

OK, I will implement with event listeners.  
Thank you.

---

<div class="post-metadata">

**Author:** ![PHH](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/phh/32/94_2.png) [@PHH](https://forum.flowable.org/u/PHH)\
**Post date:** [June 5, 2017, 2:23pm UTC](https://forum.flowable.org/t/custom-history-database/611/4 "2017-06-05T14:23:59Z")

</div>

Flowable 6.1.0 isn’t far away and the async history will be easier to use than the detail needed with event listeners.

Cheers  
Paul.