Core/Transformation: Move remaining pipelineConfig to transformation service

[mathiaszinnen]

Currently, configurations for data transformation and notifications are stored and handled at the core service. This task should be handled by the transformation service. The exact implementation is highly dependent on whether we already have rabbitMQ or not. I suggest implementing rabbitMQ first so we do not have to implement event handling twice.

[mathiaszinnen]

Use node-persist for persistence?

[georg-schwarz]

So, as I understand it, the library you propose is only in-memory, or at least not sharable with other instances of the same microservice type. I would rather go with a postgres solution.

With the new insights emerging of segregating notification and transformation service, we should also split this task into two issues.

[mathiaszinnen]

Agree, I would propose closing this issue and creating new issues after rabbitMQ integration