I’m trying to do some server-side third-party API calling using
play-ws on a job schedule in my play app. It’s using the quartz scheduler. It can be a lot of requests at once but I’m using monix’s
AsyncSemaphore to limit the amount of calls to the third-party APIs so that is not an issue.
My question is would it be useful to use another execution context as per https://www.playframework.com/documentation/2.6.x/ThreadPools, or can I stick with the original one? If I were to use a new one, I would use the
fork-join-executor as it’s really just IO.