Hi Alex, there are many things to consider aside from performance, most notably the ergonomics of using and later maintaining / troubleshooting issues All of these components provide good overall performance, with some exceptions and the amount of tuning one is willing to perform.
My goto component is Netty, it has a very large user base and usually excellent performance, though to get the absolute best out of it you might need to do some configuration. My advice is that you pick the one you find is easier for you to comprehend configuration and documentation for and run tests to see if it meets your needs. More often than not, the bottleneck is in the code we write, not the code that has been done for us in the frameworks or libraries, after all, these receive far greater scrutiny and variance of use cases and have been around for longer. (2c) zoran On Fri, Dec 4, 2020 at 11:13 PM Alex Luo <kapok...@gmail.com> wrote: > > Hi Dear, > > I am writing a Camel application which is using a Camel component to expose > Http endpoint (Http Consumer), and connect to a third party Web Server > (Http Producer). > > 1) From my readings I have this list of Camel components I can use as Http > Consumer. They all offer the same functionalities in general. What are the > differences between using each one of them? And which one is performing > better in terms of TPS and concurrency? > > Camel-Jetty, Camel-Netty-htttp, Camel-Servlet, Camel-undertow. > > 2) The following camel component list can be used as an Http Producer, > Which one has better performance? > > Camel-Http, Camel-Http4, Camel-Jetty, Camel-Netty-htttp, > Camel-undertow. > > Thanks so much for your advice. > > -- > Sincerely, > > Alex -- Zoran Regvart
