Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Promoting Service Reuse within your Organization and Encouraging-SOA Success

1 000 vues

Publié le

To view recording of this webinar please use below URL:


In this session, Chris Haddad, vice president - technology evangelism at WSO2, will describe benefits gained by

Publishing managed APIs for consumption within your organization

Establishing API manager and publisher roles to foster API adoption

Extending the service governance registry to encourage cross-team (or cross-department) communication, coordination, and collaboration

Overcoming common SOA anti-patterns of ‘Not Invented Here’ (NIH) and ‘Build, and Build Again’ by using an API store
Following an API roadmap focused on increasing service re-use and enhancing IT business value

Publié dans : Technologie
  • Soyez le premier à commenter

Promoting Service Reuse within your Organization and Encouraging-SOA Success

  1. 1. Promoting Service Re-use with API Management Chris Haddad @cobiacomm on Twitter Read more about WSO2 API Manager at http://wso2.com/products/api-manager Read more about promoting service re-use with APIs at http://wso2.com/whitepapers/promoting-service-reuse-within-your-enterprise-and- maximizing-soa-success/
  2. 2. Your Service Oriented Architecture Goals • Enhance Agility – by increasing service re-use – with faster integration – efficiently upgrading service subscribers • Reduce Technical Debt – Eliminate redundancy and duplication within service portfolio [re-wire apps to standard service] – Track adoption
  3. 3. Have you reached your destination?
  4. 4. Service Adoption(Challenges) Often difficult to offer your business capabilities as a re-usable service • Delivery Concerns • Potential consumers do not trust service stability, reliability, availability, or performance • Providers have scalability concerns and lack an ability to manage consumption • Security risks prevent publishing and offering open access • Poor Re-use • Difficult to manage requirements from multiple consumers and coordinate release schedule • Few consumers adopting service • Inability to configure service per consumer • Business return requires service metering usage rates, and billing
  5. 5. Return(Service Sprawl); Teams re-build rather than re-use • Services proliferate (100s of services) and are minimally re-used • Minimal communication and coordination • Who is consuming service? • Who is writing re-usable service? • Prevalent SOA Anti-patterns • Not Invented Here (NIH) • Tight Coupling and Build again • Shared service invisibility • Teams do not know about service • Non-functional and functional requirements are not well documented • Teams can not easily map service to needed business capability
  6. 6. Refactor the portfolio and processes • How can I identify technical debt? • What is preventing service re-use, and how can I encourage service consumption? – When do consumers not know about a service? – Why do services not meet consumer requirements?
  7. 7. Promoting Service Adoption and Re-use Requires • A published service catalogue and service tiers • Demand and capacity management • Lifecycle management and workflow • Continuous provisioning and deployment • Service level management • Collaboration channels
  8. 8. Service Transformation • An API (or a service) is a business capability delivered over the Internet to internal or external consumers • Network accessible function • Available using standard web protocols • With well-defined interfaces • Designed for access by third-parties • A Managed API (or a managed service) is:  Actively advertised and subscribe-able  Exhibits high Quality of Service (QoS)  Available with Service Level Agreements (SLAs)  Secured, authenticated, authorized and protected  Monitored and monetized with analytics
  9. 9. OtherService Containers External API (Demand) API Façade Mediation / Service Virtualization / Orchestration Service Platforms API Facade Pattern within a Services Architecture
  10. 10. Service Re-use Dashboard
  11. 11. Extending Service Governance with API Governance
  12. 12. Best Practice Integration (SOA) Use Cases and Roles •API Creator • Builds, manages, and versions API • Understand business and technical requirements • Cares about usage and scaling • Seeks feedback, ratings, usage •API Publisher • Publishes, Promotes and encourages consumers to adopt APIs • Determines usage patterns and how to best monetize asset • Monitors and secures •API Consumer • Understands the interface definition • Subscribes and connects application to API • Monitors own usage and cost basis • Provides feedback and ratings
  13. 13. API Consumer Role
  14. 14. API Publisher and Creator Role
  15. 15. Roadmap 1. Define roles and responsibilities 2. Extend SOA Governance and service run-time policy into external API design, development, and consumption activities 3. Establish on-demand self-service API consumption channel 1. Analyze service dashboards and identify subscription trends 2. Relentlessly reduce technical debt through service re-use rather than re-build
  16. 16. lean . enterprise . middleware
  17. 17. References Product Page •http://wso2.com/products/api-manager/ Getting Started Guide http://d.content.wso2.com/files/WSO2APIManager-v1.0.0- GettingStarted.pdf White Papers Promoting service re-use within your enterprise and maximizing SOA success WSO2 API Manager Comparison Blogs •http://sanjiva.weerawarana.org/2012/08/api-management-missing-link-for-soa.html •http://techfeast-hiranya.blogspot.com/search/label/api%20management •http://sumedha.blogspot.com/search/label/API •http://blog.cobia.net/cobiacomm