Q: Are taps automatically multi-process? Particul...
# singer-tap-development
f
Q: Are taps automatically multi-process? Particularly if parent-child streams, are the child streams handled in a separate process or parallelized?
Looking at the SDK, I don't see any parallelism in the taps. Targets do have a max_parallelism, but I'm not sure how that actually works. Reason asking is that there is concern over how we can parallelize requesting data in the taps. It would seem child streams would lend themselves very naturally to parallel execution, but it does not appear that is currently the case. Is that accurate?
e
Might be simple if the API isn't rate limited simple smile
e
Small warning - some APIs, like GitHub, don’t like when you are using the same token to make concurrent requests
f
So how can we make this parallel then? Even if we use partitions, they don't appear to be run in parallel. So we would have to schedule separate jobs, and in our case spin up separate pods, for each parallel extract and load we wanted to run?