State Of Services

State of Services

12th November, 2009

Sanjiva Weerawarana, [email protected]

Who Am I - Overview

> Affiliations: Founder, Chairman & CEO of WSO2

Founder & Chief Scientist, Lanka Software Foundation

Visiting Lecturer, Univ. of Moratuwa, Sri Lanka

Member, Apache Software Foundation

(Emeritus) Director, Open Source Initiative

> Previously 8 years at IBM Research

Co-author of WSDL, BPEL4WS, WS-Eventing, …

Founder of Apache SOAP and Apache Web services

Member, IBM Academy of Technology2 November 12, 2009 State of Services Copyright © 2009 EDGEAPJ and WSO2

Partnership with CA

> WSO2 technology is what powers CA Catalyst Integration product to integrate CA products together (But I wasn’t invited here with that knowledge!)

> WSO2 products used WSO2 Enterprise Service Bus WSO2 Web Services Application Server WSO2 Governance Registry WSO2 Business Process Server

3 November 12, 2009 State of Services Copyright © 2009 EDGEAPJ and WSO2

About WSO2

> Founded in 2005 by pioneers in XML and Web services technologies & standards as well as open source

> Founders & lead contributors to Apache Web services projects

> Offering complete SOA platform, 100% free and open source

> Business model based on providing training, consultancy and support for the WSO2 products

> Global corporation with R&D center in Sri Lanka and offices in US & UK comprising of 75+ people

> $6m investment by Intel Capital


WSO2 Product Platform


Agenda

> Introducing SOA – 10 years later

> Standards and the standardization saga

> REST vs. WS-*

> Technology and standards adoption

> Implementing SOA

> SOA & Cloud Computing: dark cloud or silver lining?

> Looking ahead into the next 10 years

> Summary


A bit of history from 1999

> Web is everywhere

> XML is real

> XML + HTTP used to exchange business messages

> Every vertical domain has their own security, reliability and transactions protocol for XML+HTTP: OTAA, HL7, TPAML, …

> WS-* is born as attempt to standardize these protocols SOAP envelope to carry things

WSDL language to tell others what you have

Various protocols to make the stack complete


Service Oriented Architecture

> First mention of SOA in modern context in 2000 by Steve Burbeck of IBM:

> Fundamental concepts of SOA are not new Paul & I wrote a CACM paper about doing SOA with CICS!


Service Oriented Architecture

> SOA is the best practice for building distributed interconnected systems

Using well-defined interactions between systems

Moving from proprietary formats to open formats:– XML, HTTP, SOAP

Integration is dependent on external interfaces not on internal code

> SOA is the basis of all modern Enterprise Architecture


Services

> Services are application assets that provide useful function

> The service is not just the software… it is the running system

> Services are accessible in a common way across the network and organisation

> Services are re-usable building blocks that can be re-used to build other applications


Standards and standardization


Standards and standardization

> Standards are critical to achieve “well-defined interactions”

> WS-* is the interoperable standards family for SOA

> But not the only way to do SOA However this is the “English” of the system integration

world

Or the IP of the network protocol world


Standards and politics

> WS-* platform specification creation lead by Microsoft & IBM

Small team defines an initial draft spec

Feedback solicited from closed community of external partners

Result published as a draft

Iteration

de facto standard

Submit for de jure standardization

Publish as standard

> Other big guys (notably Oracle and Sun) not happy!


“Standards” galore: 150+!


SOA Standards – Courtesy of Thomas Erl


Source: http://www.ws-standards.com/relationship2.jpg

http://www.ws-standards.com/relationship2.jpg

Standards – 10 years later

> Core platform now de jure standards SOAP, WSDL, WS-Policy, WS-Addressing, WS-Reliable

Messaging, WS-Security, SAML, …

> Do they work? Tremendous efforts put into interoperability testing by

both standards organizations and (especially) Microsoft

Lots and lots of success stories published

A few edge cases still remain here and there

– Vendors have demonstrated true dedication to achieving practical, “it just works”, interoperability


REST vs. WS-*

> Representational State Transfer Underlying architecture of the Web

Lighter weight approach to integration using the Web directly instead of “tunneling” a new abstraction over the Web

> If the shoe fits, put it on .. REST does not provide same QoS as WS-*

– New entrant: rest-star.org

But if its good enough for the problem, use it

WSDL 2.0 can describe REST services

> Big battle in years 6-9, now everyone has moved on ..


Technology & standards adoption

> WS-* powered SOA now accepted as the de facto standard for complex system integration problems

First time in history of computing that every vendor supports the same set of interoperability protocols

> Core platform adoption is solid Basics (SOAP, WSDL, Policy)

Security

Reliability

> Transactions adoption is growing

> UDDI is dead with no real replacement (maybe little need?)


Gartner’s 2009 Technology Hype Curve


Implementing SOA


Implementing SOA

> Common mantra: “You can’t buy SOA, you have to build it”

> SOA is not a technology, its an approach! It is best enabled by the use of a set of interoperable

technology standards but just using them does not make your system an SOA solution


Focus on loose coupling during design implementation

> Location and Access Scale up, failover, contingency

> Programming Language Work with available skills

Integrate old and new

> Stack/Vendor No tie in to a particular proprietary solution

> Time Asynchronous interactions avoid gridlock


Good SOA implementation patterns

> Thin slice implementations “Guerilla SOA”

> Iterative project plans

> Prove the concept to the business

> KISS


SOA and Cloud Computing


Evolving computing landscape


Software distribution channels

> Download and run on customer hardware Data center: Private

Resource sharing: None implied

Scaling: Single to cluster

> Buy appliance and plug-in Data center: Private

Resource sharing: None

Scaling: Single box

> Buy virtual machine and run on cloud platform Data center: Private or public

Resource sharing: Virtual machines

Scaling: Single to cluster to elastic

> Software as a service Data center: Public

Resource sharing: Multi-tenant

Scaling: Cluster or elastic


SOA & cloud computing


Into the future …


In 10 years …

> XML & WS-* based SOA will be the like Java is today for server-side application development

English v1 is firmly established

Most of the world is speaking good English

> Impedance mismatch between programming languages and communication modalities will force a new English to be formed

XML-*.next + Java.next + WS-*.next + SQL.next all in one package that makes distributed application development truly seamless

> Entire process will start again …


Summary

> WS-* powered SOA is the new English of the computer world

> Phenomenal adoption and vendor support in a short time

> Cloud computing takes loose coupling to another dimension, augmenting SOA

> Build, DO NOT BUY, SOA


QuestionsEmail: [email protected]

Web: http://wso2.com

Blog: http://sanjiva.weerawarana.org/

State Of Services

Technology

cloud computingnovember

publicresource

privateresource

powered soa

amp

soa

standards

integration