title: Is asynchronous programming required in Micronaut?
body: <p>There is a bit of a tradeoff with reactive/async programming - you trade simpler, more readable/maintainable code for improved performance.</p>
  <p>If you are planning to do blocking operations in a Micronaut REST application, is it considered terrible practice to execute these on the HTTP request serving threads?</p>
  <p>If you were to increase the size of the HTTP request serving threadpool in Micronaut so that it was similar in size to that of a regular HTTP framework's thread pool, for example non reactive Spring MVC / Tomcat, would you expect Micronaut's performance characteristics to be similar to those of Spring MVC running on Tomcat?</p>