Variable history table

As camunda store all the past variables of past instances in this ACT_HI_VARINST table.

If we consider an enterprise organization this table will get so mighty? isn’t it?

Is this an efficient and up to the mark to store past variables like this?

Just a thought if camunda can store only one xml or json per instance !!


You can implement custom handling of history events and then write these things anywhere and in any format you like. You will not be able to use Camunda’s querying capabilities then. See for details.

You can also switch off history or lower the history level to reduce the amount of historic data. Lastly, you can partition history tables to speed up access operations if your database offers such a feature.