Regular Workflows versus In-Memory Workflows
The table compares and contrasts the regular workflow with the in-memory workflow.
| Regular Workflows | In-Memory Workflows |
|---|---|
| During each activity execution, process states are persisted to the database and distributed cache. | During each activity execution, process states are written to the local cache. |
| Input, output, and intermediate documents are persisted to the file system. | Input, output, and intermediate documents are maintained in the local cache. |
| Each activity is considered a transaction. | The entire workflow (consisting of multiple activities) is considered a transaction. |
| When a transaction is committed, all workflow changes (process states, documents, and record related data) in that activity are committed. | When a transaction is committed, record related data in the workflow is committed. If the saveonsuccess flag is on, data from the local cache (process states, documents) is committed. |
Copyright © Cloud Software Group, Inc. All rights reserved.