There is no "better." You simply look at your needs and match. E.g.,: Apache: Does it all. Uses lots of ram doing it. Nginx: Does some of it. Uses little ram

There is no "better." You simply look at your needs and match. E.g.,: Apache: Does it all. Uses lots of ram doing it. Nginx: Does some of it. Uses little ram doing it. I used to use apache, but I didn't need it's bulk. Nginx suits me just fine. You just need to pick something and move on to coding. In the end a webserver is only a means to an end: your startup. If you need to change later to scale, do it then. You just need to launch right now.