Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote 0 down vote favorite

1) Apache2+uWSGI+NGINX(for static)

or

2) NGINX + uWSGI

share|improve this question
1  
Depends what your requirements and criteria are, which you haven't provided. Questions that rely heavily on one's opinion of one software package versus another aren't a good fit for this site. That being said, if you're going to be running nginx regardless, why would you add Apache in unless you require something that it provides that nginx does not? – Shane Madden Dec 15 '11 at 6:46
Thank you! I`m novice in this area and don`t know all features of this configurations! but I want know the direction to my future learning! Sorry for my English. – Michael Dec 15 '11 at 17:01

closed as not constructive by Shane Madden, Ladadadada, Michael Hampton, Ward, rnxrx Aug 25 '12 at 5:48

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.

1 Answer

up vote 0 down vote

If you're starting from scratch and don't have any Apache specific dependencies in place that drop it for straight NGINX

fewer points of failure and a server that has a much smaller memory footprint especially when scaling to larger number of requests -- though a bit trickier to setup in the beginning since NGINX is relatively new to the hosting scene compared to Apache and has significantly fewer examples to call upon

though again - this is if you are starting from scratch and don't need anything Apache specific

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.