Async (blocking) vs non blocking

[billoneil]

No description provided.

[sachin-walia]

@billoneil I am wondering if you can provide some information on where and how to use IO Pool. I understand for blocking cases such as DB, Redis, API calls it is suggested to use worker pool or blocking handler. I wonder if there is any use case for using IO pool. How would those handlers and their response body looks like.

[billoneil]

@sachinwalia2k8 I'm not too experienced in the non blocking side myself as most of my systems use databases. A large portion of the built in Undertow handlers are non blocking though.

A good example would be ProxyHandler which proxies HTTP requests to another server. I thought the ResourceHandler was non blocking but it looks like not all of the implementations are non blocking so we must assume they can block.

The Undertow dev list might be a better resource for that question undertow-dev@lists.jboss.org.

[sachin-walia]

Thanks @billoneil BTW your website and your github project really sold me on using Undertow for building our microservice infrastructure. Hopefully over time we'll get rid of our Spring boot based services and just use Undertow. I am using Undertow with Dagger for DI and it is really an awesome combination.

[billoneil]

@sachinwalia2k8 that's great to hear. Once you know many of the common libraries that all of the frameworks already share it's not too difficult to just implement them yourself. There are of course some tradeoffs but I would willingly lock myself into a library that I fully understand instead of using abstracts where I'm not quite sure what is going on. I'm personally not the biggest fan of DI due to some previous bad experiences but Dagger is the one that looks most promising to me.