Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
If we are not talking about a huge number of simultaneously processed requests, then the choice here comes down mainly to what is more familiar / more convenient to configure: Apache or Nginx.
Nginx + php-fpm - more economical in terms of memory consumption and OS threads, keeps more simultaneous connections in conditions of limited resources, due to this, many call this option faster (on single requests without load, the difference is, of course, imperceptible).
Apache + mod_php5 (or Apache + mod_proxy_fcgi + php-fpm) - many prefer it because they are used to the syntax of its config and .htaccess (which is absent in Nginx in this form).
There is no single answer here.
Much depends on who will support the future infrastructure and what this web application was originally developed on (because there are many dependent rules in .htaccess that are unprofitable to rewrite in nginx).
If the product is developed and tested primarily under Apache (and, possibly, with some other Apache modules): definitely Apache. Otherwise - you need to think depending on the extensibility scheme, in providing support for the solution, etc.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question