-
Feature Request
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
7.18.0-alpha1
User Story (Required on creation):
We allow our customers to design many processes(can easily exceed 50+ ) using our process designer and allow different process persona's to instantiate and interact with those processes during runtime. We make use of camunda process engine - 7.17
Camunda Process engine makes use of in-memory LRU cache for following Deployment metadata.
protected ProcessDefinitionCache processDefinitionEntityCache;
protected CaseDefinitionCache caseDefinitionCache;
protected DecisionDefinitionCache decisionDefinitionCache;
protected DecisionRequirementsDefinitionCache decisionRequirementsDefinitionCache;
protected BpmnModelInstanceCache bpmnModelInstanceCache;
protected CmmnModelInstanceCache cmmnModelInstanceCache;
protected DmnModelInstanceCache dmnModelInstanceCache;
As you know, this in-memory cache is backed up by DB persistence. We are using distributed cache (Memcache with near and remote cache) for -
1) Better management of memory footprint. Deploying many processes, results in high memory usage, and we want to govern size of in-memory cache using nearCache/remoteCache of Memcache.
2)Any un-deployment of process gets sync-up on all nodes. Invalidation of cache get sync-up on all nodes.
Functional Requirements (Required before implementation):
We allow our customers to design many processes(can easily exceed 50+ ) using our process designer and allow different process persona's to instantiate and interact with those processes during runtime. We make use of camunda process engine - 7.17
Technical Requirements (Required before implementation):
Make all attributes of DefinitionEntities and ModelInstance Entitities used by above deployment caches, to implement Serializable interface, so that we can use above entities in distributed cache implementation like Memcache.
Limitations of Scope (Optional):
Hints (optional):
This is the controller panel for Smart Panels app
[CAM-14644] Make all attributes of ProcessDefinitionEntity deploymentCache as Serializable
| Assignee | New: Miklas Boskamp [ miklas.boskamp ] |
| Link | New: This issue is related to CAMTEAM-239 [ CAMTEAM-239 ] |
| Description |
Original:
h3. User Story (Required on creation): Make all attributes of ProcessDefinitionEntity deploymentCache as Serializable
h3. Functional Requirements (Required before implementation): h3. I have many Process definitions. I can not use distributed cache ( Memcache) to store the Deployment Metadata like ProcessDefinitionEntity, CaseDefinition, BmnModelInstance as all attributes inside of them doesn't implement Serializable interface that is required for distributed caching !! h3. Technical Requirements (Required before implementation): h3. I can not use distributed cache ( Memcache) to store the Deployment Metadata like ProcessDefinitionEntity, CaseDefinition, BmnModelInstance as all attributes inside of them doesn't implement Serializable interface that is required for distributed caching !! h3. Limitations of Scope (Optional): h3. Hints (optional): |
New:
h3. User Story (Required on creation):
h3. We allow our customers to design many processes(can easily exceed 50+ ) using our process designer and allow different process persona's to instantiate and interact with those processes during runtime. We make use of camunda process engine - 7.17 h3. Camunda Process engine makes use of in-memory LRU cache for following Deployment metadata. protected ProcessDefinitionCache processDefinitionEntityCache; protected CaseDefinitionCache caseDefinitionCache; protected DecisionDefinitionCache decisionDefinitionCache; protected DecisionRequirementsDefinitionCache decisionRequirementsDefinitionCache; protected BpmnModelInstanceCache bpmnModelInstanceCache; protected CmmnModelInstanceCache cmmnModelInstanceCache; protected DmnModelInstanceCache dmnModelInstanceCache; h3. As you know, this in-memory cache is backed up by DB persistence. We are using distributed cache (Memcache with near and remote cache) for - h3. 1) Better management of memory footprint. Deploying many processes, results in high memory usage, and we want to govern size of in-memory cache using nearCache/remoteCache of Memcache. h3. 2)Any un-deployment of process gets sync-up on all nodes. Invalidation of cache get sync-up on all nodes. h3. Functional Requirements (Required before implementation): h3. We allow our customers to design many processes(can easily exceed 50+ ) using our process designer and allow different process persona's to instantiate and interact with those processes during runtime. We make use of camunda process engine - 7.17 h3. Technical Requirements (Required before implementation): Make all attributes of DefinitionEntities and ModelInstance Entitities used by above deployment caches, to implement Serializable interface, so that we can use above entities in distributed cache implementation like Memcache. Limitations of Scope (Optional): h3. Hints (optional): |
We are closing this ticket as part of our backlog grooming. Reasons:
- It is very unlikely that we will implement this
- We did not receive sufficient evidence that this ticket is important
- The ticket description is not clear
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Hi suhas-kulkarni,
Thank you for coming up with a feature proposal.
To better understand your goals could you please elaborate on the following questions?
Please give as much information as you can. We need to fully understand your feature request before we can decide if it would make sense for a broader userbase to have.
Best,
Miklas