Divert DB writes to external/application cache for Savepoints

Hi Team,

As you know currently when we have savepoint in our flow execution i.e. asynchronous after or before or User Task or Timer etc… we save the current execution state in camunda database and we create job in camunda database. So that if there is application restart of failover then it execution flow is recovered from camunda database by same instance or other instance.

Now my question is can we override this behavior and divert/move execution state to external/application cache?
In this case we will save DB hits and achieve recovery from cache by putting execution state in database. This final database save will happen only in case of recovery.