Apache vs nginx

Some big players used it in the past. It's not exactly a niche thing.
Guess I just like lightweight software. Probably because most of my hardware is aging and I dislike throwing out machines if they're still in working condition.
Started using lighttpd to run a small site with 24/7 streaming music and a small forum. No RoR involved whatsoever, but I understand that lighttpd is quite beloved in that community. Had Alpine on an old Sony Vaio and figured I'd give it a shot. Stable, fast, lightweight, efficient and easy to configure. What's not to like?
I've since changed distros (migrated to Apache, 'cause I'm quite familiar with it) but I still enjoyed the time spent fiddling with lighttpd. Apache is the old standard, but, as an user has pointed out ITT, it does feel like it's starting to lag behind the competition.
Also, the dude who created musl will tell you that Apache is inherently racist. Nevermind the fact that the creator has said that "Apache" is a play on "a patchy" webserver and also said he admired the Apache's prowess in war. Dude's a fag.

if you wanted load balancing, you'd use haproxy

node.js

no

I like apache better but nginx is a bit faster

you're never going to generate enough traffic to see the performance of nginx so just use whatever is easier and has what you want.

>thread per request in 2018
**BREATHES IN HEAVILY**

HHHAAAAAAAAHAHAHAAHAAAAAAAAAAAAAAAAAAAAAAAAAAHHHHHHHHAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHHAHAHAHAHAAHAHAHAHAHAHAHAHAHAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHAAAHAHAHAHAAHAHA

It's not.

>thread per request
You fucking what?

apache2 is a literal joke
t. nginx user

Apache uses a thread per connection, which isn't as dire as one per req, but still it's fucking wasteful.

Vibe.d

didn't bother with google yet, but is there an equivalent to that nginx's rtmp module for apache or lighttpd? might be interested in the latter mostly

>All the cool shit like hls/dash streaming and load balancing is locked behind a completely insane thousands of dollars per instance license

As far as I know, all of that either works in the free version or there's modules that support them. I do know for a fact hls streaming is supported by the rtmp module, because that's what my site uses.

Unless OP is servicing thousands and thousands of people it's not going to matter.

Apache = pajeet tier ooga booga doo doo people browser
Nginx = High IQ white man browser

Attached: 1411447205818.png (589x273, 30K)

You don't know what this thread is about.

because you cant into rtfm

apache is a browser now huh?

Im sure there is a plugin to make that happen.

I use Apache for PHP and other scripts through mod_fcgid. Nginx for static content and as a reverse proxy to SSL/HTTP2 the connection out to client.

Running PHP on nginx was a miserable experience comparable to running PHP as a module inside Apache. If it wasn't for that I might have switched from Apache to nginx completely.

Because its Russian

>tfw you learn that it's pronounced engine-x
I'd been calling it nignex in my head. Thankfully I never speak to people so I didn't make a fool of my self.

nginx is more "lightweight" so to say.

But this comnparison generally doesn't matter, because either your tooling is tailored towards Nginx or Apache and you use what's necessary.