I have a spring-webflux API which, at a service layer, needs to read from an existing repository which uses JDBC.
Having done some reading on the subject, I would like t
1) Use of subscribeOn
is correctly putting the JDBC work on the jdbcScheduler
2) Neither, the results of the Callable
- while computed on the jdbcScheduler, are publishOn
the parallel
Scheduler, so your map
will be executed on a thread from the Schedulers.parallel()
pool (rather than hogging the jdbcScheduler
).