Again, depends on if you're doing a lot of IO, especially if you want request-based IO parallelism. It's worth mentioning that even if you're IO-bound at your

Again, depends on if you're doing a lot of IO, especially if you want request-based IO parallelism. It's worth mentioning that even if you're IO-bound at your DB, running an async application server now means you don't need to tie up a thread waiting on it. Memory usage aside, you more or less don't need to think about threads much, whereas a threadpool (one waiting on IO) is something you have to actively manage.