Nginx vs Apache Webservers: Main Differences

This video is about main differences between Apache and Nginx web servers.

[lastmanustanding]

I like to call it "Engine X".

[aettic]

Fascinating, I had no idea you could use them in conjunction. Thank you for the detailed video.

[MxSmack]

This is very insightful, thanks very much for sharing this!

[thikee]

nice video! It helped me to understand the up- and downsides from each ☺️

[vivekshetty]

Thanks, the video was very informative

[TheXV]

you have a mistake at 5:00. I think you mean Nginx leans towards URL not filesystem evaluation

[danysamsalmon]

Nice video. It is pronounced as 'Engine X' though. Cheers.

[filthyE]

Help, Apache ate my server for breakfast!

[anrdaemon]

nginx supports dynamic modules for a very long time, your information is(was) not correct. The fact they are not widely available does not change the fact they do exist.

[ImreBertalan]

This video is misleading in some aspects, specially related to NginX.
3:26 NginX is able to do "per-directory-configuration", it is just not called that. Read more about "location" and "try_files"
5:11 Doesn't check the files, indeed, but it does able to use htaccess files to lock access to certain URLs or pages

[anildhage]

Just for laughs, I like the way he says Ngeeenx.

[kommunismusarbeiterjonny]

Nginx Sometimes works and then randpmly Just dont wwhhhyyy the best Thing Is It is saying it works in the rpi

[_Jayonics]

Although it would initially seem nginx is significantly faster. If you configure Apache to use h2 (http2) along with PHP multi processing. The speed difference becomes near minimal.

I mean, I'm running my webserver on a raspberry pi and it first it was horribly slow, but once I enabled these features the difference was night and day.

[HindiUniversalFacts.]

not clear, you are just reading the presentation ??/

[___xyz___]

I think I actually prefer "en-jinx". "Engine-X" is a bit too pretentious to me.

[beners]

music was distracting but excellent breakdown!

[Pulkit__]

Wow, can someone speak english. I don't know why, I have been coding for now nearly 5 years and now even I am an Android developer, but NginX is still over my head.
Guess I should make a new droplet and work on my NginX skills

[anrdaemon]

You forgot to clearly explain the main difference between the two: while (as you said) nginx built with "request first" mentality, mapping requested URL to the filesystem (or to the backend proxy), Apache HTTPD works the other way around, and builds relation from filesystem to the request. This makes it impossible to remove all active content from Apache HTTPD webroot - you will need at least a wrapper file to begin bootstrapping your application through RewriteRule or FallbackResource. Another core difference is how configuration is interpreted. Apache HTTPD merges all eligible configuration blocks, making it sometimes hard to find configuration errors. nginx won't do that - its configuration is declarative and explicit.

Oh, and of course, next time please name things properly. It's "Apache HTTPD", not just "Apache". "Apache" is an organization.

[drewerving]

You should pronounce the names right if you want to be taken seriously sir. However, great video. Thank you

[wexwexexort]

Don't use music next time, please. How can I hear you with that loud music?