SOA: Making the Paradigm Shift Part 6 of N - The Current State of SOA and How to Make the Paradigm Shift – ROUGH DRAFT

The Transition

Old World	New World
Monoliths	Services
Tightly Integrated	Loosely Coupled
Process Centric	Workflow Enabled
Islands of Automation	Integrated Service Networks
Accountability	Results
Bending the enterprise to the will of technology solutions	Adapting technology to meet the needs of the enterprise

The Current State of SOA

Most of what is labeled “SOA” today is really just Bottom-Up JBOWS. It’s not that these home-grown, spring-like-weeds services are not valuable. It’s just that there is no vision or alignment with the business drivers of the organization. Developers are kings and left to do what they want and there is no standards or governance. It’s no great surprise when such “SOA” fails.

• Lack of Compliance/Governance
• Reduce the ‘unintentional tyranny of the application programmer
• Security, Common Policy Repository, Common Schema, etc
• Deployment, Management, and Change are ad-hoc
• Centralized Management Experience
• Improve Execution Visibility
• Changes are risky and disruptive
• (Service Hell)
• Low Adoption Rate
• Nothing to encourage the construction and reuse of services
• Existing tools instigate retraining more than reuse of skills

Getting There

• Improve Current Project Approach
• Ensure SOA is part of the implementation

• Leverage guidance, products, and information in current project workload

Be Practical

• Avoid Common Pitfalls

• Gain immediate results