Joined June 2013
·
Achievements
49 Karma
0 Total ProTip Views

Nephila Komaci
Have at least one original repos where PHP is the dominant language

Nephila Komaci 3
Have at least three original repos where PHP is the dominant language

Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos

Forked
Have a project valued enough to be forked by someone else

Charity
Fork and commit to someone's open source project in need
While it certainly helps an enormous amount on a single server, APC (and all other in-process caches) isn't a scalable solution because it can't maintain cache coherence beyond a single host. As soon as you have more than one web server, you need to use something distributed such as memcached or redis.
For front ends, both nginx and haproxy are faster than varnish and will scale to higher connection counts. They don't necessarily do the same thing, but there is a lot of overlap for proxying, balancing, failover, caching, SSL unwrapping etc that they can make a better job of than varnish.