Hi,
Would it be possible to add a Redis connector to EasyMorph? Redis is widely used for caching, session storage, and as a fast key-value store in many data architectures, and being able to read from (and optionally write to) Redis directly would be really useful for several scenarios:
-
Pulling cached lookup data or reference tables into EasyMorph workflows
-
Reading queue data or real-time metrics for reporting
-
Writing processed results back to Redis for consumption by other applications
A basic connector supporting common operations like GET, SET, MGET, and hash operations (HGET, HGETALL) would cover most use cases.
Interesting combination with CallPython
A native Redis connector would pair nicely with the existing CallPython action for more advanced workflows. For example:
-
Use CallPython to run a complex Python script that processes data and writes results to Redis (using
redis-py) -
Then use a native Redis action in a subsequent step to fetch that data back into EasyMorph for further transformation or reporting
This pattern would allow leveraging Python's flexibility for heavy lifting or custom logic, while keeping the main EasyMorph workflow clean and easy to follow. Redis would provide a fast and interesting option for passing data between Python and EasyMorph steps.
Future possibility: Redis as a Server trigger
Down the line, it could also be interesting to add Redis as a trigger option for EasyMorph Server tasks — for example, triggering a workflow when a message arrives on a Redis pub/sub channel or when a key is added to a list/queue. This would enable event-driven workflows and tighter integration with real-time data pipelines.
Thanks!