Apache vs NGINX

If you're into web development, you have undoubtedly heard of Apache and Nginx. They're both open source web servers, but they have different strengths, and both are worth considering as part of your web architecture choices. Is speed at all costs your thing? Or extensibility? In this video, Martin Keen explains how these web servers work and then breaks down the tradeoffs of each solution (spoiler: it's not an either/or answer).

#AI #Software #Dev #lightboard #IBM #MartinKeen #Apache #NGINX

[kavyeshs]

we can install Apache's modules separately. but nginx needs a re-compilation of binary if want to enable a new module. and another main difference is Nginx is event driven while apache is process driven. which means nginx can handle much more request on single thread but apache create new thread for every request. which makes nginx fast/more performant

[dieguitoboy]

Didn't really explain the differences between the two or gave any examples for which is better on certain aspects. The title of the video wasn't delivered

[im-a-trailblazer]

This man has talent, and he is able to explain it in a very enjoyable way, and he can write backwards very fast. I need to up my game man...

[samjones]

Thank you very much for this lesson! You’ve unlocked a bit of a mystery for me as I’m beginning my cloud journey! 🥳

[khasanbekdev]

Great, I always enjoyed videos of IBM Tech, can you make a video explanation for ASGI and WSGI servers.

[andygordon]

Fanatistic quick explanation of different considerations when looking at web server performance. Great start to answering the question. Thank you

[kamarton]

I've been using both for many years, and I like the modules and configuration of nginx much better.

[unspoken]

I have been looking for a video like this for a long time! Outstanding work!

[gosnooky]

It should also be noted that Apache uses a multi-threaded architecture with each request running in its own thread, while NGINX uses a single-threaded architecture with an event loop. Because of this, NGINX can handle many more simultaneous requests and is what gives it its speed advantage. In programmer terms, Apache acts like Java, NGINX acts like NodeJS.

[mohammadalaaelghamry]

Great resource of knowledge, high quality, very concise and to the point. I so much appreciate it. Thanks.

[snowywinter]

Such a pleasant and knowledgeable presenter. Fantastic delivery.

[chalingui]

OMG Martin is the man. One day making exBEERiments and the other day teaching about web servers <3

[chwaee]

TLDR/TLDW: Apache is older but more mature (extensions) while nginx is newer and faster. Both can be used rather interchangeably though.

[evgenii.panaite]

Amazing, always love your way to uncover technological nuances ❤

[cguevaraaguilar]

Thank you very very much! Finally I understood it in a simple, clear and practical way. I'm your fan!

[pieter]

4:48 The difference between Apache and Nginx

[appaloosa-marketing]

Thank you, british man & ibm. Perfect explanation 🙏

[pankajoctdogra]

Nice presentation, pls make video of cloud native app architecture with financial services application

[chadzulu]

This explanation helped me a whole lot! Thanks so much.

[entalpa]

You didn't mention that Nginx can do Rate Limiting, WAF and more...Nginx can be a lot of faster by tweaking the settings for your use case.