Ignoring the condescending tone in many place, there are many great points are made here in identifying gotchas and offerring approaches. But characterizing the "bad" aspects as "EAI 2.0" and the alternative approaches as "SOA" is off-base.
The concepts of decoupling, location transparency, etc. are not unique to SOA. Looking up the address of another component isn't a breakthrough, nor even SOA-inspired. The specific approach of using service proxies isn't an "SOA requirement." It's simply one implementation possibility. The implication that if you're not doing it this way you're not doing SOA is incorrect, IMO. -Rob
