TABLE OF CONTENTS
Data storage management includes configuration and resource provisioning of structured/unstructured data. While integrating applications as well as data in real-time, storages play a crucial role. Storages within Alumio can be utilized for multiple purposes. While there are many use cases, this article will throw some light on the basics.
Storage For Caching
If you go to any specific storage, you will come across a few fields such as Name, Identifier, Description, Settings (the kind of storage), and much more.
You can also Enable pruning of storage items that allows you to set up the Time to live. You can set it to 1 hour (suggested) and all data will be removed from the storage every hour. There are options to select time units such as Hours, Days, Weeks, Months, etc that allow you to manage your storage requirements.
From the top, you can visit the Entities section, which will list the information which will eventually go through the system. Alumio can apply some filters for the data to verify certain conditions such as whether or not the data had passed through the system before. They can be applied in the Incoming configuration that is linked to the storage.
To get a fair idea of the aforementioned things, here is a quick example for you.
Step 1: Create a Demo Storage by filling in the fields mentioned above as per requirements.
Step 2: Go to the left panel and go to Connections > Incoming.
Step 3: Create (or search for) an incoming configuration that is using the cache storage mentioned above. Now, you can add some filters within the incoming configuration. For instance, in the video above, a Filter called Filter previously stored entities has been used.
Step 4: As you click on the Run Incoming button at the top-right corner, the data will start flowing into the designated storage.
Step 5: Re-visit the Demo Storage set up. Go to Entities and click on the Refresh button (top-right).
Step 6: Now, the storage information will be listed here. You can view any information by clicking on the Identifier. Each identifier stores a whole object.
Here are some additional notes curated for you!
Note 1: If you have added a filter (Step 3), Alumio will implement it. For example, if you have added Filter previously stored entities as a transformer, Alumio will verify the incoming data and won’t add it to the storage if it is already there.
Note 2: You can modify any data with a specific Identifier by opening and removing the object (data). Subsequently, you can save another object within the same Identifier.
Note 3: From the Entities list, you can Delete them from the Actions tab.
Note 5: A storage can also be used to map data easily in Alumio, thanks to the extensive range of mappers and filters it has! This has been discussed in another article: Mapping and Filtering Data Using Entity Transformer In Alumio.
Storage forms the backbone of interconnected and data-driven operations that spur a business. A requirement might arise where you have to store information at one moment while checking it at another. There might be a route that fills some information in the storage initially, while another route picking up the same information at a later stage. The possibilities are endless and Alumio can make every integration work smoothly!