sync. Process and persistence overhead

[metalli93]

Hi community,

As a newbie I want to implement a fully synchronous process with Activiti. My process contains a chain of service tasks and each task is connected to a JavaDelegate class. When a message arrives as a Java object, I put it in the process variables map and start the process. Each JavaDelegate class modifies the message and the last task saves the message in my business DB.

What I want to know is, if the process variable (in my case a big object) is persisted after each service task in the activiti db? If so, it would be a real overhead for my process. Is such a process maybe the wrong use case for activiti? 

Regards,
Wahid

[trademak]

Hi,

Yes it's persisted every time you change the object. But it's persisted as a blob, so it shouldn't be too much of a problem if the object isn't really big (like > 100kb or so).
Make sure the history level is not set to full, because then every change is also stored in the history tables.

Best regards,