Apache HTTP Server vs. Apache Traffic Server vs. Java vs. Kestrel Comparison Chart

Apache Traffic Server™ software is a fast, scalable and extensible HTTP/1.1 and HTTP/2 compliant caching proxy server. Formerly a commercial product, Yahoo! donated it to the Apache Foundation, and currently used by several major CDNs and content owners. Improve your response time, while reducing server load and bandwidth needs by caching and reusing frequently-requested web pages, images, and web service calls. Scales well on modern SMP hardware, handling 10s of thousands of requests per second. Easily add keep-alive, filter or anonymize content requests, or add load balancing by adding a proxy layer. APIs to write your own plug-ins to do anything from modifying HTTP headers to handling ESI requests to writing your own cache algorithm. Handling over 400TB a day at Yahoo! both as forward and reverse proxies, Apache Traffic Server is battle hardened.

Kestrel is a cross-platform web server for ASP.NET Core. Kestrel is the web server that's included and enabled by default in ASP.NET Core project templates. Kestrel supports HTTPS, HTTP/2 (except on macOS), Opaque upgrade used to enable WebSockets, Unix sockets for high performance behind Nginx. Kestrel is supported on all platforms and versions that .NET Core supports. Some browsers require granting explicit permission to trust the local development certificate. Project templates configure apps to run on HTTPS by default and include HTTPS redirection and HSTS support. The Kestrel web server has constraint configuration options that are especially useful in Internet-facing deployments. There's a separate limit for connections that have been upgraded from HTTP or HTTPS to another protocol (for example, on a WebSockets request). The default maximum request body size is 30,000,000 bytes, which is approximately 28.6 MB.