1 / 20

SOA: Successful Adoption & Barriers

Explore successful business scenarios, technologies, and governance of Service-Oriented Architecture (SOA) along with common barriers to adoption. Embrace roadmaps for effective implementation and learn about the alignment of service and system ownership.

peyton
Download Presentation

SOA: Successful Adoption & Barriers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SOA – Successful Adoption and BarriersIDC Service-Oriented Architecture Conference 2005Rick Robinson, IT Architect, IBM EMEA WebSphere Lab Servicesrick_robinson@uk.ibm.com

  2. Agenda • What works? • Barriers • Roadmaps • Summary

  3. What Works?Business scenarios, technologies and governance

  4. What Works? Business Scenarios • Multi-channel • Multiple technology channels, e.g. desktop, browser pervasive • Multiple brands • Intermediary, B2B or dot.com models • Small to large • Service aggregation e.g. financial portals • dot.com integration e.g. Amazon, e-Bay • New Applications • Well-targetted process automation • Integration or Consolidation • Bottom-up integration architectures of reasonable ambition • Single view of data

  5. What Works? Technologies • Legacy • e.g. CICS “routing transaction” using simple structured data formats • … increasingly migrating to Web services • Enterprise Application Integration (EAI) • XML interfaces and message formats • Communication through EAI technology e.g. asynchronous messaging • Custom API frameworks provide application support • … increasingly migrating to Web services • Web services • Many current uses of Web services are for basic point-to-point integration • Some more advanced organisations have built SOA infrastructures with extensive use of Web services • … becoming more common as Web services mature

  6. Channel Owners System Owners Operations Director What Works? Aligned Service and System Ownership Online bank Account Management Reseller channels, e.g. supermarkets Payments Branches Service Gateway etc. Corporate Bank ... etc. ... • One layer of services • Organisation matches service architecture • Obvious owners of services and supporting infrastructure

  7. BarriersMismatches, trust and … governance

  8. Barriers: Mismatches • Narrow drivers, broad ambition • Are current business goals to reduce cost or develop new business? • Is the level of sponsorship consistent with the scope of impact? • Inappropriate combinations of risk • Pilot project, new technology • Production project, conservative technology • Many other combinations! • Scepticism – adopting SOA successfully requires cultural change • “It’s nothing new” • “The technology doesn’t work” • “It’s not for us”

  9. Change to irrelevant optional schema Service implementation changed or substituted Change to relevant optional schema or mandatory schema Barriers: Trust • If SOA uses intermediaries to insulate service consumers from changes to service implementations, how do services consumers know when to re-test? Application Service 1 Service 2 Service 3 Service Z No need to test Test No need to test • Until services are trusted, regression testing will be performed in all cases • Automated testing scripts and tools can be used to minimise impact

  10. Barriers: Governance Store Client (Orders) Order Services Accounts Store Client (Catalogue) Product Services Product Management Sales Management Client Service Bus Pricing Services ERP Product Management Client etc. etc. ... etc. ... • No clear point of ownership for common services • Infrastructure owned by IT, clients and back end systems owned by lines of business • Tends to result in a proliferation of variations of “common” services dedicated to specific channels

  11. Our strategy is SOA I need a new mortgage system Enterprise Architecture Group Can it be operated? Infrastructure SOA Project ITA Does it advance our strategy? ! ITS Architecture Operational Review Board TDA Barriers: Governance

  12. Roadmaps

  13. There is no roadmap … … but there are many individual steps to take in an order that makes sense to your organisation. • Standards Based Model for all Service Interaction Aspects • Important aspects include protocols, interface definitions, message formats, APIs, directories etc. • Service Enable Legacy Systems and Applications • Analogous to JDBC enablement of databases for J2EE • Implement a High Quality of Service Infrastructure • Asynchronous messaging, assured delivery, security, transactions and compensation etc. • Establish a comprehensive model and implementation of different types of service • Business process vs. business transaction vs. technical service vs. external service vs. legacy service etc. • Service directory and re-use strategy • Establishing the development culture, publishing and discovering services, internally and externally etc. • Establish organisations and processes for governance and ownership • Enterprise Architecture governance, service ownership etc.

  14. Summary

  15. Summary • SOA has been repeatedly proven over the last decade (at least!) • Open standard and product support is increasingly rapidly in sophistication and maturity • In it’s broadest form, SOA is an approach to Enterprise Architecture, and there is no skirting the difficult issues associated with that • But a big-bang approach is not mandated … • … a flexible, incremental approach moulded to business needs and strategy is the most likely to succeed

  16. End

  17. Timings • 3 minutes intro • 3 slides in first section finish on 5, 7, 9 minutes • 1 minute bridge • 4 slides in second section finish on 12, 14, 16, 18 minutes • 1 minute bridge • 1 slide in last section finishes on 21 minutes • 4 minutes wrap-up and contingency

More Related