Matt Braiser points out that despite having many uses and providing multiple solutions, SOA applications cannot solve all problems. Instead, their performance must be monitored and the business goals that they are meant to achieve must be well defined:
As for SOA skills, in my work I see architects being a bit weak in handling problems with nonfunctional requirements, like performance, scalability, general stability and the ability of the application to stay up and deal with the user load. My advice is that they should better learn what the business requirements actually are in terms of number of users and response times.
Check out the full post, SOA Applications: Why Businesses are Using SOA, Skills Architects Need, from SearchSOA.