Balancing on Nginx, processing on Apache, statics on S3 AWS. What are the pitfalls?

M

Max Khrichtchatyi2013-11-28 08:20:13

PHP

Max Khrichtchatyi, 2013-11-28 08:20:13

The project architecture is as follows:
1 Nginx server (balancing)
3 Apache servers (executing scripts)
All statics are stored in Amazon S3
, etc.
I didn’t want to assign my server for statics right away, but now it’s interesting to hear your opinion about using such a bundle. What do you think if Apache is replaced everywhere with Nginx? In general, your opinion.

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

A

Alexander Korotaev, 2013-11-28
@aavezel

On Apache, how do I understand php?
Then: The question is put incorrectly: What do you think if apache mod_php is replaced everywhere with fastcgi? The result is obvious:
1. mod_php eats a lot of resources like a pig, but fast as a jaguar.
2. fastcgi weighs like a bird, but brake like a hippo.
Conclusion: Why did you even ask? :-)

Y

Yuri Yarosh, 2013-11-28
@d00mko

Apache in this case does not make sense - take php-fpm + nginx via file sockets, and you will be happy. Regarding statics - it makes sense to use Cloudflare, S3 big Overkill for a similar task. Chop the forest with nuclear warheads.

K

kenny_opennix, 2013-11-28
@kenny_opennix

Nginx+php-fpm+cache statics on nginx, I can withstand high loads.
apache is a superfluous fact here, statics and varnish can be distributed.