Presentation titleHow WSO2 helped save Euro 500K anddeliver SOA solutions faster

By Stephen OostenbrinkThe Ministry of Infrastructure and the Environment

How WSO2 helped

save Euro 500K and

deliver SOA solutions faster

Stephen OostenbrinkEnterprise Architect and Technology Evangelist

The Ministry of Infrastructureand the Environment

Is your IT

outsourced?

Have you seen

SOA projects fail?

Is the SOA promise not

being delivered?

The challenges of

successfully executing

a SOA strategy in a

complex outsourced

environment

The ministry of what?

The ministry is facing

major challenges

Enterprise architecture is part

of the governance organization

EnterpriseArchitecture

ApplicationManagement

ServiceManagement

InformationManagement

We have outsourced our IT

Complex environment

(simplified view )

KPNProlocation

SSC ICT

DICTU

Atos

Rijksconnect

Internet

Diginetwerk

RijksconnectDiginetwerk

civilian

company

authorities

company

BASEregistries

BASEregistries

BASEregistries

authorities

The SOA promise

BuildingBlocks

BaseRegistriesRegistries

System

Monolithic Systemws ws ws

The SOA headache

1st rule of integration: It will fail, you don’t know when!

2nd rule of integration: It will FAIL, you don’t know when!

3rd rule of integration: When it fails parties will be pointing at each other.

The rules of Fight Club

What happened to

reuse?

Not spending money where

it adds business value

Business value

Commodity

Application

Middleware

Infrastructure

Why were our SOA

projects failing?

1. Failed in communicating

our SOA vision and strategy

2. Lack of SOA expertise

and experience

Concept Practicevs

3. Tension between short term

results and long term goals

4. Old school thinking

“Insanity: doing the same thing over and

over again and expecting different

results.”

Albert Einstein

5. Not in control of the

chain

6. Reinventing the wheel

KPNProlocation

SSC ICT

DICTU

Atos

Rijksconnect

Internet

Diginetwerk

RijksconnectDiginetwerk

civilian

company

authorities

company

BASEregistries

BASEregistries

BASEregistries

authorities

ESB(Product A)

ESB(Product D)

ebMS adapter(Product E)

ESB(Product C)

ebMS adapter(Product G)

ESB(Product B)

ebMS adapter(Product F)

7. Missing a reliable platform

to build on

8. Not taking manageability

into account

Time to rewrite the

rules

“I enjoy being the architect, because I

can break the rules and create my own.”

Richardo Semler

“Don’t choose new wallpaper when the

building is on fire.”

Fred Corzilius

Balance between

pragmatic and idealistic

Focus on the foundation

Evangelise SOA vision andstrategy

Build skills and expertise Implement basic platform

Get involved

Selected an ESB focussing

on 4 key criteria

Dutch governmentinteroperability standard

Manageability

Modular setupOpen source

Comply with the Dutch government

interoperability standard

WUS (WSDL, UDDI andSOAP) + WS-RM

ebMS (ebXML MessagingService)

Large message standardPKI certificates

Open standards are a must,

open source is preferred

WSO2 ESB looked promising

but no ebMS support

Proof of concept to prove WSO2

ESB could be made compliant

4 weeks 4 use casesCompliancy proven

andbasic ebMS adapter+ =

ebMS adapter is

enterprise ready

The foundation required

additional functionality

Fully automateddeployment

Insight in service usage

Governance Registry

Business Activity Monitor

KPNProlocation

SSC ICT

DICTU

Atos

Rijksconnect

Internet

Diginetwerk

RijksconnectDiginetwerk

civilian

company

authorities

company

BASEregistries

authorities

Centralizing connectivity and moving control to

the application level

ESB

ESB

ESB

ESB

Enterprise Service Bus

Governance Registry

ebMS adapter

Business Activity Monitor

Enterprise Service Bus

Enterprise Service Bus

Enterprise Service Bus

Enterprise Service Bus

Identity Server

Next steps: roadmap

Shift from web service toAPI model

Enhanced manageabilityfrom application level

Improve and expand theplatform

API Manager

This shift will result in

regaining control

In control

Dependency

Business value

Commodity

€€€€ €€€

€€

Application

Middleware

Infrastructure

Now

Application

Middleware

Infrastructure

Near future

WSO2: the good, the bad and the ugly

Products

(what we like) (room for improvement)

Accessibility

Documentation

Support

Code comments

Communityinvolvement

Summary

Evangelise

Chain management

Expertise and experience

Right platform

New paradigm In the trenches

Right partners

People and technology

Was the title a teaser?

No, saving more than € 1

million in 3 years

ESB products phased out € 950KReduced development, deployment and operational costs € 250-500KReduced infrastructure and middleware costs € 200-300KEstimated savings next 3 years € 1.400-1.750K

Questions?

Thank you