Working at a start up where multiple investors came into the same round at different valuations; so yes, they should, it makes sense as different people bring different things to the table.
The main reason I can think of is the single point of failure in regards to a NAT instance. With the only other alternative being giving EIPs to every host that needs internet access. I would like to see a more robust solution and HA for the NAT instance. Especially if you're doing any kind of heavy proxying, couldnt you max out the NAT instance's uplink at some point? Anyone have ideas?
My scenario was load testing, to generate 1M outgoing connections we need 17 IP aliases, aliasing doesn't work on EC2, so we had to spawn 17 instances just for this.
I didn't tried elastic IPs for this, not sure it will work for outgoing connections.
Granted, there has been a lot of PHP bashing lately and by and large, those who bash PHP the most - whether they are right or not - generally have little to no meaningful experience with it and are re-iterating whatever they've read about it. Fact.
However, this is just stockholm syndrome, plain and simple. Fabien is the author of Symfony.
