

By IO heavy I meant db operations or other external requests. When the request handler starts, it waits for the IO to be completed. While it waits, it can accept other requests and so on, so the bottleneck is the IO in my case, not the request parsing.
I imagine it like this (imaginary numbers):
- DB operation: 20ms
- Express request handler: 1ms
- Brhama request handler: 0.5ms
Which case, it wouldn’t matter which http framework to use. However, there are probably other use-cases.
So, for example, online editors that store state in huge jsons and has frequent backup can benefit from it. That’s actually great, good luck with it!