> For some reason Apache gets bad rap for being old and slow while in reality it's still a pretty damn good at what it does. There's a few actual reasons for w

> For some reason Apache gets bad rap for being old and slow while in reality it's still a pretty damn good at what it does. There's a few actual reasons for why this might be the case, because in some configurations Apache can indeed be somewhat slow. .htaccess: if you don't disable this mechanism, the web server might do a bit too much I/O, their docs describe it all nicely and it's good to pay attention to this, because you won't always need .htaccess in the first place https://httpd.apache.org/docs/current/howto/htaccess.html https://httpd.apache.org/docs/current/howto/htaccess.html mod_php: some don't bother setting up PHP-FPM properly (assuming that you want to run PHP apps with Apache) and instead reach for the legacy module which has considerably worse performance than the alternative https://cwiki.apache.org/confluence/display/HTTPD/PHP https://cwiki.apache.org/confluence/display/HTTPD/PHP Once I get some more motivation, I'll do a real world comparison of Apache, Nginx and probably Caddy as well in a variety of workloads. My intuition tells me that Apache will still be slower, but not to a degree where it would be a non-starter for the majority of the projects out there.