My top ten principles for evaluating SOA preparedness:
SOA is real. It is not a quick fix. It is a ten year journey that requires considerable planning, just like an e-commerce implementation.
SOA is built upon 15 years of experiments in creating highly distributed computing environments that take into account everything from load balancing, software distribution, security, and data management including meta data management and registry.
SOA will only work if organizations lead with manageability. SOA by its very nature demands the aggregation of IP from many different sources. Scalability within SOA will come from management – not development.
SOA will only work if it is implemented within the context of a business process orientation.
SOA is predicated on leveraging business services that represent the component parts of your business.
SOA requires a container that creates a composite application.
SOA requires standards across all vendors implementations of SOA.
SOA assumes that you will begin to write applications differently – as a series of tightly defined services intended to be loosely coupled.
SOA assumes that each component part is equipped with a clearly implemented web services interface based on standards.
SOA dictates that change is the norm since this approach mimics the way a business operates.
Link