Some months ago we were sitting around at the office at $DAYJOB discussing the relative merits of active/active vs. active/standby architectures.
The discussion centered around the polarities of "easy to deploy" vs. "more resilient and worth the effort"
One of my colleagues was sleep-deprived so he swears he doesn't remember saying this suddenly decisively stated:
Objects in motion remain in motion... Objects at rest tend to be broken.
Which pretty much sums up the case for active/active. Over the past several years I've noticed a recurring theme of standby environments falling over, version skew, major outages resulting...