Definitely, if you're working on a project where web server performance is very important, rather than just a dinky link dump like my personal site, Apache is probably something you should move on from. But I'm assuming that if you're working on that kind of scaling problem, you're not looking to fix small problems here and there with an .htaccess file.
NGINX (pronounced "engine x") has a more robust feature set for dynamic content and is more performant at scale.
There are definitely pros and cons to each solution, and the amount you "feel" the difference between them will largely depend on how complex your site is and what your scaling needs are.
Here's a good side by side comparison from the beginning of this year, if you're trying to decide which solution is right for you.
never met a part of the stack I didn't like. sr. engineer at clique studios in chicago, perpetual creative hobbyist, bird friend, local gay agenda promoter. she/her. tips: https://ko-fi.com/carlymho
Definitely, if you're working on a project where web server performance is very important, rather than just a dinky link dump like my personal site, Apache is probably something you should move on from. But I'm assuming that if you're working on that kind of scaling problem, you're not looking to fix small problems here and there with an
.htaccessfile.What would you recommend moving away from Apache to?
PS. Really great article. Thanks for putting this together. I found it helpful and I am sure so many more will too.
NGINX (pronounced "engine x") has a more robust feature set for dynamic content and is more performant at scale.
There are definitely pros and cons to each solution, and the amount you "feel" the difference between them will largely depend on how complex your site is and what your scaling needs are.
Here's a good side by side comparison from the beginning of this year, if you're trying to decide which solution is right for you.
Okay, I definitely learned something today, because I had no clue how NGINX was pronounced, haha