First, bear in mind that the reverse proxy mechanism that we are going to describe in this chapter should not be considered as a long-term solution. It should be employed as a temporary architecture in problematic cases such as the following:
When you already have Apache installed with complex configuration files that can hardly be ported to Nginx, or if you do not have the time or the will to completely switch to Nginx
When your system operates a frontend system management panel such as Parallels Plesk, cPanel, or other solutions that automatically generate Apache configuration files
When a functionality that your project or architecture requires is available with Apache but not with Nginx
In any other case, a complete switch to Nginx would be a better choice. Chapter 7, From Apache to Nginx provides a streamlined description of the process.