With the reverse proxy configuration that was elaborated in the previous chapter, the presence or absence of specific features wasn't much of a problem. This is because Nginx would simply have to differentiate between static and dynamic content, and in consequence serve static file requests and forward dynamic file requests to a backend server. However, when you start to consider Nginx as a possible full replacement for your current web server, you had better make sure that you know what's in the box. If your projected architecture requires specific components, the first thing you would usually do is check the application features. The table listed in the following section lists a few of the major features and describes how Nginx performs in comparison to Apache.