Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to use nginx as a reverse proxy for Google App Engine application to support naked domain as described here. If I use this scheme, will all the traffic go through the server that hosts nginx or client will connect to App Engine directly? Can it be a bottleneck for performance and availability?

share|improve this question
up vote 2 down vote accepted

Using that method, all your traffic would run through the NGINX server so that would be a bottleneck, and you'd have to make sure it had enough capacity to work well. It would also cause some latency (Approximately 2x latency on every request, because your client would have the latency connecting to NGINX then NGINX would have the latency of connecting to AppEngine)

share|improve this answer
What about using the reverse proxy along with varnish + memcache as an inline cache? You'd probably save some money on GAE CPU time. ::raises eyebrows:: – Evan Plaice Jan 3 '13 at 21:26

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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