Commentary--A growing number of companies are implementing SOA projects to lower IT integration costs while improving the time it takes to make changes to business units. However, of those companies that have begun deployment, many are held up in the early implementation phase. This has resulted in a number of organizations either scaling down or abandoning their SOA deployment plans.
There are fairly common mistakes to avoid when implementing an SOA project, and best practices are starting to emerge based on successful, enterprise-wide deployments. To follow are the 10 most common mistakes companies make when implementing an SOA project. Recognize and avoid these potential pitfalls to successfully get your SOA initiative off the ground.
1. Taking a shotgun approach
When attempting to move to an SOA, companies often take a shotgun approach and don’t take into consideration which services are actually being used, often times web-enabling more than is necessary. Service enabling everything is costly and may not be necessary.
