# CQRS pattern using Flowable Event Engine

**URL:** <https://forum.flowable.org/t/cqrs-pattern-using-flowable-event-engine/6437>\
**Category:** Flowable Engine\
**Created:** [July 25, 2020, 6:40am UTC](https://forum.flowable.org/t/cqrs-pattern-using-flowable-event-engine/6437 "2020-07-25T06:40:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![svanga](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@svanga](https://forum.flowable.org/u/svanga)\
**Post date:** [July 25, 2020, 6:40am UTC](https://forum.flowable.org/t/cqrs-pattern-using-flowable-event-engine/6437/1 "2020-07-25T06:40:23Z")

</div>

Hi Team,

Can we use Flowable Event Engine for [CQRS](https://github.com/cer/event-sourcing-examples/wiki/WhyEventSourcing) pattern?

regards  
sri

---

<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:** [July 30, 2020, 5:09pm UTC](https://forum.flowable.org/t/cqrs-pattern-using-flowable-event-engine/6437/2 "2020-07-30T17:09:58Z")

</div>

Yes. In fact, a process/case is an ideal candidate to be the ‘command’ part on receiving an event.

What exactly are you looking for?

---

<div class="post-metadata">

**Author:** ![svanga](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@svanga](https://forum.flowable.org/u/svanga)\
**Post date:** [March 10, 2021, 8:15am UTC](https://forum.flowable.org/t/cqrs-pattern-using-flowable-event-engine/6437/3 "2021-03-10T08:15:52Z")

</div>

Thanks for information. Can we assume that Runtime Tables and History Tables are following the principle of CQRS with exist Architecture? Because runtime data is replicated in History tables by sync and async mechanism

---

<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:** [March 18, 2021, 8:34am UTC](https://forum.flowable.org/t/cqrs-pattern-using-flowable-event-engine/6437/4 "2021-03-18T08:34:40Z")

</div>

Can you elaborate on that concept, not something that rings a bell immediately?

But yes: flowable has the option to either have synchronous history (100% in sync with the runtime) or asynchronous.