Do we need to continue to have a native job manager in WebAPI? Or could Arachne provide this functionality?
Either way, we'd want to make sure that any WebAPI elements are not tied directly to the job management framework as this was a pain point in v2.x of WebAPI.
Noting from discussion: when running in a load-balance environment with WebAPI, job management in v2.x is problematic since there were assumptions made in the job manager to cancel any "old" jobs at startup.
Do we need to continue to have a native job manager in WebAPI? Or could Arachne provide this functionality?
Either way, we'd want to make sure that any WebAPI elements are not tied directly to the job management framework as this was a pain point in v2.x of WebAPI.
https://manib.hashnode.dev/spring-batch-with-spring-boot-3