Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Governance for a connected ecosystem

Governance for a connected ecosystem

SOA / API / Application governance reference architecture, #wso2con14sf

E71c1071861e4f8526d75feb67371bd1?s=128

Nuwan Bandara

October 29, 2014
Tweet

More Decks by Nuwan Bandara

Other Decks in Technology

Transcript

  1. Governance for a Connected Ecosystem Nuwan Bandara Senior Lead, Solutions

    Architecture WSO2
  2. What is so called “Governance” ! | # $ Processors

    / Standards / Policies / Agreements / Rules / Analytics
  3. Why do we need governance Best practices (processors) drive projects

    to success Standards are scientifically proven for repeatable tasks Policies & Rules can control situations Agreements provide awareness and avoid surprises Analytics provide an overview of a situation
  4. Governance: A technical elaboration During design phase During the development

    phase During the test phase During the run time During the review phase Government of the people (and their activities), by the people (and institutions), for the people (and their activities)
  5. So long “Services” Governance Services governance received much love from

    SOA during the past decade Services are not in the limelight anymore Services have become a small piece of a larger ecosystem
  6. Comprehensive SOA governance Data Services Orchestrations Business Services Utility Services

    Workflows Mediation APIs Applications Frameworks / SDKs % Business APIs % %
  7. API based ecosystem vs SOA model Same concept different a

    interpretation APIs are actively advertised End user requirements drive API design APIs are more concrete and self contained APIs create a bigger impact to the end user SOA API
  8. Say hello to “API Governance” # & ' ( (

    ' )* + Security / Versioning / LCM / SLA / Throttling / Monitoring
  9. What is beyond APIs ? Application frameworks / Wrappers Software

    Development Toolkits (SDKs) BaaS / MBaaS Application Lifecycle Management (ALM) DevOps automation & policies
  10. Governance expanding to the external developer LCM for Applications Team

    Management Collaborative Development Review Test policies Deployment policies Scaling Policies / HA Policies Dependency / Resource Management
  11. New IT delivery model

  12. Factors of a unified governance story Metadata / dependency governance

    Service governance Workflow governance API governance Application governance DevOps management Continues improvements via intelligence
  13. The connected ecosystem

  14. Governance concerns for a connected space Shadow IT Service /

    API / SDK / Application discoverability Improper change management Lack of transparency in different layers Labor intensive manual tasks
  15. A Governance model for a connected ecosystem Services workflows /entitlement

    / mediations APIs SDKs Applications dependancies service   endpoints code Sequences   /  workflows   (BPEL) endpoints  /   polices SLAs documents policies metadata  /   (Schemas  /   Contacts) API  endpoints Contracts  /   policies SDKs team  /   collaboration code , versioning - monitoring #  deployment / discoverability / store 0 LCM/ALM
  16. WSO2’s take on the reference model Services workflows / entitlement

    / mediations APIs SDKs Applications dependancies service   endpoints code Sequences   /  workflows   (BPEL) endpoints  /   polices SLAs documents policies metadata  /   (Schemas  /   Contacts) API  endpoints Contracts  /   policies SDKs team  /   collaboration code , versioning - monitoring #  deployment / discoverability / store 0 LCM/ALM
  17. // Questions ? Thank You!