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

Question

PHP

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.

Answer 1

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? :-)

Answer 2

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.

Answer 3

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