Methods for scaling a system/strategy node...

Curious how others or the industry handles this problem. Suppose I have a running system, which is essentially a full pipeline. Feature engineering -> signal processing -> strategy - > execution. Is bundled in modular components, build using Nautilis Trader and custom solutions.

Now its running, but im working on other strategies, that often use some of the same features or transformers, import patterns. However, I now want to modify or edit those. Since the running strategy is integrated into this system, it becomes difficult to say the least. 5k custom features, multiple data classes, 20 transformers etc.

Is the solution to duplicate the node and leave it isolated, or is it integrated? I opted for integration, but think this could get out of hand with multiple strategies/versioning as i work forward.

Curious what others do. It would in essence be separate repos, similar frameworks but with varied feature calculations/custom data objects/configs. Each running there own persistence, i/o, logs, etc.

How does the general fund approach this problem if a pod executes multiple assets/timeframes etc