Unfiltered: When to Choose Netty

Question

I did a quick test in unfiltered, comparing the throughput of both the berth and netty as the base connection handlers. It just serves (with memory) the image and runs a load test. My results are that there is no significant difference in performance.

In addition, I get the impression that both have similar scaling features as well as suspend connections.

Moreover, unfiltered is kind enough to give us very similar (if not the same) interfaces for both frameworks, so you cannot say that it is easier to use the other.

So, I wonder why unfiltered give us these two choices? is there any scenario when you choose netty above the pier (or vice versa)?

Answer 1

My personal thoughts: I used the built-in pier only as a container of servlets. Using netty, I can spoof http packets every time, configure my own HTTP data store. IMO, I think they are both sharp knives, but netty can turn into a needle if you want.