Differences

This shows you the differences between two versions of the page.

--- transformations:sharedmemory [2021/09/03 18:13] – created dmitry
+++ transformations:sharedmemory [2021/09/03 18:23] – [Key-value storage] dmitry
@@ Line 17: / Line 17: @@
 ^ Key ^ Value ^
 | Path  | D:\Input files  |
-| Last reload date  | 2021-09-03  |
+| CustomerDB\Last reload date  | 2021-09-03  |
 To obtain a value, one should know the key. Keys and values can be added and removed on demand with the help of the "Shared memory" action. The shared memory is stored in the centralized repository. Therefore any EasyMorph workflow can read (recall) and write (remember) keys and values in the shared memory at any moment as long as it has access to the repository.
+\\
 =====Use cases=====
 The shared memory can be convenient in many cases:
@@ Line 29: / Line 30: @@
   * Workflow variable - While project parameters are constant and don’t change during a workflow run, the shared memory values can be set, removed, and changed in a single workflow
   * Lightweight data store - Sometimes, using a relational database to store and share just a few values looks like overkill. The shared memory can be more appropriate for such cases.
+\\
+=====Remarks=====
+It is recommended to use the backslash (\) to create nested keys.
+The same access restrictions as for data connectors apply.
+The shared memory supports simultaneous operations from different computers as long as they can access the same repository.
+Values are remembered in the shared memory and recalled in native [[syntax:types|EasyMorph data types]]. Errors can’t be remembered by design.
+You can store large text objects, such as JSON in the shared memory.
+All stored data is encrypted and can't be accessed from outside of EasyMorph.
+Depending on repository location, network performance, and size of the stored keys and values, the shared memory can handle up to 100 operations per second.