Like I’m sure many of us do, I have need in a few of my transformers to map a part of incoming data to the correct value for the outgoing side. An example would be Product A = Product B. I’ve been using a simple database setup to manage these style cross-references.
Recently the database server crashed and I rebuilt my most critical cross-reference structure as a Storage until we could restore the database(maybe 10 or 11 storage entities mapping in and out shipping conditions). I certainly didnt(and dont) want to hard-code these in a transformer as values may change over time.
This made me question if this is acceptable use of Alumio storages? Up until now I’ve just been using them more as a “cache” of entities, but is using the Storage in the form of a simple collection of permanent records not acceptable? I worry that one day I might log in to find the Storage has been “flushed” by an upgraded or something.
Maybe there is a better way to handle these mappings all together?