Sanjiva WeerawaranaCEOWSO2 February 2010

SOA Governance in the Cloud

Sanjiva Weerawarana – CEO

• Founder, Chairman and CEO of WSO2.

• Previously IBM Research for 8 years. Lead WS-* platform development.

• Co-author of WSDL, WS-BPEL and other specifications.

• Author of Web Services Platform Architecture book.

• Apache Software Foundation Member.

• Lanka Software Foundation Founder, Director and Chief Scientist.

• Visiting Lecturer Univ. of Moratuwa, Sri Lanka.

WSO2

• Founded in 2005 by acknowledged leaders in XML, Web Services Technologies & Standards and Open Source

• Producing entire middleware platform 100% open source under Apache license

• Business model is to sell comprehensive support & maintenance for our products

• Venture funded by Intel Capital

• Global corporation with offices in USA, UK & Sri Lanka

• 80+ employees and growing

WSO2 SOA platform

WSO2 cloud computing

• Cloud virtual machines: software virtual machines– WSO2 products as Amazon EC2, VMWare & KVM images

• Cloud connectors: connecting the cloud to the enterprise– Cloud Services Gateway– Service Accelerator

• Cloud services: SOA software as a service– Governance as a Service– Identity as a Service

• Cloud middleware: building multi-tenant services & applications

Engagement Model

• Quick Start– Combination of consulting, training and POC development in one week by

WSO2 on-site team working hand-in-hand with your team

• Development Support– On-going support for your engineering teams

• Production Support– Full 24x7x365 enterprise support– Regular service packs and updates to keep your system secure and

robust

What is the Governance Issue?

• Who let the dogs out?!

• SOA opened the door to much more open Enterprise IT– More departments started offering services– Integration became easier

• More integration• Less central involvement• More ad-hoc approaches

• There needs to be a response– But not just closing the door – Intelligent approach to allowing SOA to grow

SOA “challenges”

• The SOA bunfight:– Interdepartmental rivalry becomes rewritten – Lack of clear responsibilities and domain ownership– Rival groups fighting for ownership of domains or business services

• The SOA vicious circle:– Current funding models are based on BUs– No incentive for a BU to make services available to a wider audience– Service initiatives cannot get funded

• The SOA bandwagon:– Everyone is “fully committed” to SOA– Plenty of “SOA initiatives” to make the current infrastructure “SOA-

enabled” but no real changes to structure, processes or architecture– All talk – no action

A high level definition of Governance

• A decision-making and accountability framework for IT resources

• Governance includes:– The framework for decision-making– How to allocate responsibility across the organisation– Processes involved in making decisions– Metrics for monitoring the effectiveness of the organization

• Aims to provide visibility and control as well as a clear decision making process

• Governance is not the management of IT – but setting the right framework for IT management

SOA Governance best practices

• Establish early• Organizational acceptance for Governance• Communicate relentlessly• Automate• Govern the entire service lifecycle• Anticipate mixed technologies• Monitory,access & report business value• Consider cross organizational boundaries

How to turn that into reality?

• The typical approach– Hire a consultant or repurpose an architect to come up with a “SOA

Governance Strategy”– Run a long RFI process to buy a complex highly expensive product– Go through purchasing to buy a pair of HA machines to run it on– Work with your DB team to setup databases and access– Hire more consultants to install and configure it– And so on

• The WSO2 approach– Register yourself online in 5 minutes– Configure your new WSO2 Governance Registry to do the most common

Governance tasks – Simple online training and documentation for you and your team– Iteratively improve your Governance – If necessary, you can move your Registry onto your own hosted systems

anytime using pure 100% Open Source supported code

An effective start to SOA Governance

• Policies– All services must be:

• WS-I compliant• Tested• Have been approved by the governance committee

• Processes – Services are promoted from:

• Design Test Staging Production Deprecation• At each stage a checklist is filled in

• People– Each service has one or more technical and business owners– Access to create, read, modify, promote services is restricted/controlled by user

and group– Access control is completely hierarchical

• E.g. Define the accounting team and give them access to the accounting services

Registering your domain

• The administrator registers the domain– Proves ownership by adding a page to the top-level domain or modifying DNS

entries• Once the domain is registered the administrator can add users, add

adminstrators, and configure many aspects• The domain then gets its own login• In addition, by adding a DNS entry, you can configure the OpenID model• The domain can be themed and the organization’s logo incorporated into the

theme

WSO2 Cloud Governance homepage

Adding users

• The administrator can simply add users and assign them to roles

• Upcoming releases will sync with existing LDAP and offer User Provisioning APIs

• Each part of the Registry can have permissions– For example, everyone can read all service descriptions, but only the

accounting team can modify and approve accounting services

Customize it!

• Simple customizations include– Theming– Configuring your definition of a “Service”– Defining the lifecycle of your services, WSDLs, XSDs, etc– Setting up notifications to the right users about changes

Other features and benefits

• Selectively expose some services to the public or to partners– Because the service is securely hosted in the cloud, there is no

requirement to set up proxies

• Supports federation between an internal Governance Registry and the Cloud– Internal Registries can federate resources from the Cloud Governance

Registry

• Supports command-line clients and other tools querying and updating cloud entries from inside the firewall– As long as clients can make secure HTTPS requests to WSO2’s hosted

servers, clients can automatically publish and query the Cloud Governance Registry

Demo

Technology

• Powered by market-proven WSO2 Governance Registry

• Hosted version is multi-tenant enabled version of WSO2 Governance Registry

• Few customizations have been disabled– Involving code insertion– Will be enabled in the future

WSO2 Openness Promise

• Any software you download from us is always open source

• Any service you use from us will support all applicable interoperable protocols and support relevant open data standards

• Any cloud virtual machines or appliances you buy from us will allow you to take complete control of your data

• For all services, cloud virtual machines and appliances, we will provide a “one button” mechanism to get a complete data export that can be loaded onto our corresponding open source product(s)

• No ifs, no buts, no gimmicks

Open Source, Open Standards, Open Data, Open Services

WSO2 Cloud Services vision

Thank you

Questions?

Resources

• Contacts:– Sanjiva: sanjiva@wso2.com– Paul: paul@wso2.com– Business information: bizdev@wso2.com

• Governance Registry:– Cloud: http://governance.cloud.wso2.com – Download: http://wso2.org/projects/governance-registry

• Articles:– Getting started: http://bit.ly/cKtsqJ– FAQs: http://bit.ly/cGLE54