title: Spring MVC to Spring Webflux migration - block vs subscribe
body: <p>Let's imagine a scenario where there's an old app written using Servlet stack and you decide to migrate it to a Spring Webflux. Let's also say that first thing to migrate is <code>RestTemplate</code> to <code>WebClient</code>.</p>
  
  <p>What would be preferred way of handling <code>Mono</code> or <code>Flux</code> that <code>WebClient</code> returns? Calling <code>block</code> seems okay solution since app uses <code>RestTemplate</code> which blocks anyway. <code>subscribe</code> should be a bit nicer since it has a callback, but maybe you have to wait to be able to continue. Also, with <code>subscribe</code>, do we need to handle a <code>Disposable</code> and, if yes, how, because I'm not sure where is the best place to call <code>dispose</code> on it?</p>
  
  <p>And one more question regarding JDBC. How dangerous is to use <code>Schedulers.boundedElastic()</code>? From my understanding, having a separate thread pool should help especially if Netty is used. It's not ideal, but could it be a temporary solution until R2DBC drivers reach 1.0.0? What if app uses Tomcat? Is the situation better since Tomcat by default has more threads?</p>