sartography
/
spiff-arena
mirror of https://github.com/sartography/spiff-arena.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Data Stores in 5 mins (markdown)

jbirddog 2024-01-22 13:14:00 -05:00
parent 7cf0111a1b
commit 7b809315c2
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Data-Stores-in-5-mins.md

@ -7,6 +7,9 @@
1. Or a Data Store could be added with reads and writes modeled in the diagram 1. Or a Data Store could be added with reads and writes modeled in the diagram
1. There can be many types of Data Stores, each handle the structure and persistence of the stored data 1. There can be many types of Data Stores, each handle the structure and persistence of the stored data
1. Data Stores are implemented in the backend and must be registered with SpiffWorkflow 1. Data Stores are implemented in the backend and must be registered with SpiffWorkflow
1. When a Data Store is added to a process model, the type of Data Store and its identifier is defined
1. To/From arrows are then drawn which cause data to be put it/taken from task data
1. They work a lot like data objects, main difference is the data persists outside of the process instance
## Current Data Stores ## Current Data Stores
@ -14,5 +17,13 @@
1. Allows storing any valid JSON blob 1. Allows storing any valid JSON blob
1. The entire blob is read/written when accessed 1. The entire blob is read/written when accessed
1. Very flexible but not optimal for large datasets
1. Stored in the backend's database, one row per instance
### ### JSONFileDataStore
1. Allows storing any valid JSON blob
1. The entire blob is read/written when accessed
1. Very flexible but not optimal for large datasets
1. Stored in a file that is committed to git along with process models
1. Good for small static global data that should be included in PRs/promoted to other environments