What does being bulletproof even mean? Let&#x27;s talk through this with an example, not drawn from programming: let&#x27;s talk about stopping actual bullets. When Operation Iraqi Freedom started, US troops were issued flak jackets, which do what they suggest - catch flak, i.e. shrapnel from bombs. They were not, despite what one might think, bulletproof vests. As OIF continued on, as forces transitioned from fighting conventional forces to fighting insurgency, it was decided that actual bulletproofing was required. So everyone was issued ceramic plates that inserted into the front and rear of the flak jacket. They were ceramic, unlike the metal plating on an armored vehicle, because as it turns out, simply stopping a bullet that&#x27;s going at over 2,000 feet per second is a great way to break a ribcage. So the ceramic plates are designed to shatter on impact, spreading the force of impact over a larger surface area. Bulletproofing a person is a different task than bulletproofing a tank. And there are downsides to bulletproofing a person - they can&#x27;t run as fast with 15 poinds of antiballistic ceramic strapped to them, and it turns out that ceramic doesn&#x27;t breathe as well as, say, cotton. So your bulletproofed servicemember is now more vulnerable to heatstroke, which is a real problem in Iraq in the summer, when daytime temps can routinely exceed 120 degrees.<p>Bulletproofing, either in the literal or the metaphorical sense, is a series of tradeoffs and compromises. The idea that there&#x27;s one right set of compromises for every HTTP server out there, not just in terms of safety but in a myriad of design decisions, is simply wrong.