Created Data Stores in 5 mins (markdown)
parent
904facd839
commit
7cf0111a1b
|
@ -0,0 +1,18 @@
|
||||||
|
# Data Stores
|
||||||
|
|
||||||
|
1. Allow BPMN Architects to define custom data models that can be shared across process instances
|
||||||
|
1. ClientA wants to deploy a website that will find a recipe based on selected ingredients, or allow the user to add an ingredient
|
||||||
|
1. Not adding an ingredients table to the backend
|
||||||
|
1. A Service Task could be used (postgres to to custom recipe backend)
|
||||||
|
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. Data Stores are implemented in the backend and must be registered with SpiffWorkflow
|
||||||
|
|
||||||
|
## Current Data Stores
|
||||||
|
|
||||||
|
### JSONDataStore
|
||||||
|
|
||||||
|
1. Allows storing any valid JSON blob
|
||||||
|
1. The entire blob is read/written when accessed
|
||||||
|
|
||||||
|
###
|
Loading…
Reference in New Issue