wso2 and 2 degrees case study

WSO2 and 2degrees Case-‐study

Agile, Mobile Services Development via

an SOA

© WSO2 2012. Not for redistribution. Commercial in Confidence.

Neeraj Sa9ja -‐ So%ware Development Manager, 2degrees Mobile NZ Ltd Waruna Ranasinghe – Associate Technical Lead, Member IntegraBon Technology Group, WSO2 Asanka Abeysinghe -‐ Director, SoluBons Architecture, WSO2

About WSO2 •  WSO2 is the World’s only… •  lean middleware company •  on-‐premise and cloud (private/public) middleware plaLorm •  complete (data to screen) open source middleware company •  Founded in 2005 by acknowledged leaders in XML, web services •  technologies, standards and open source •  Funded ($11M) by Intel Capital and Quest So%ware •  160+ employees in USA, UK, Spain and Sri Lanka •  10 books published, 100+ technical arBcles, 30 PhD candidates, 2 PhDs •  Sri Lanka – center of excellence for Open Source •  Leading source of Apache Commi\ers outside the US •  Largest per-‐capita Open Source contributors in the world •  Leading source of Google Summer of Code winners

Selected Customers

hKp://wso2.com/about/customers

WSO2 Middleware

Deployment Choices

5/17/12 5

StratosLive Public PaaS

Stratos Private PaaS

Carbon On-‐Premise

Or, any combinaBon of these.

(Same programming model across all deployment choices)

WSO2 support engagement model

-  QuickStart -  Development

Support -  Development

Services -  ProducBon

Support -  Turnkey

SoluBons

2degrees – A Brief History

-  Wireless Telco Landscape in NZ in 2007-‐2008 -  Duopoly – Exorbitant prices and stale products -  No moBvaBon for innovaBon -  High barrier to entry

-  2degrees Mobile Limited -  Set-‐up in 2007 -  IT Team set-‐up in 2008 -  Launch in 18 months -  Team of 5 people in IT, 2 focussed on SOA

2degrees – WSO2 Alliance: A Brief History DESIRED APPS/PRODUCTS/SERVICES RANGE

2degrees – WSO2 Alliance: A Brief History

-  2degrees IT Requirements -  DisrupBve InnovaBon -‐ DifferenBators -  Complex workflows, Simple Interface -  Leverage web-‐service technology -  Flexible, configurable integraBon with Network Elements -  Rapid response to compeBBon -  Robust, scalable, reliable technology -  Decision to adopt SOA and light, flexible, scalable technology

stack –Web services, ESB, N.E.

Supplier SelecBon Approach

Demo briefs With scenarios sent

to all suppliers

Demos by suppliers

Create shortlist

Technical Q&A

Create shortlist

Get proposals

Review & select

IBM Oracle Mule WSO2 Apache Sonic Open

Oracle Mule WSO2

2degrees – WSO2 Alliance: A Brief History CAPABILITY MATRIX

Developing DifferenBators – TOP UP

13

1.  Set up Customer sets up Auto Top Up in “Your 2Degrees”. Customer registers their card, and the amount they want to top up with each Bme.

Systems/backend: > IN – enables balance noBficaBon for MSISDN > @billity – stores amount > Flo2Cash – validates & stores credit card

2. Balance trigger When customer’s balance drops below $2.50, customer receives a text message asking whether they want top up from their credit card. A “Y” reply will trigger the payment and top up.

Systems/backend: > IN – triggers the text message when balance goes below $2.50 > Recharge gateway -‐ sends the text message to customer and awaits reply

3.  Payment / top up Customer replies “Y” to authorise/confirm payment

Systems/backend: > Recharge gateway -‐ “looks up” customer’s amount from @billity > Recharge gateway – requests Flo2Cash to process $X payment against e-‐token > Recharge gateway (on confirmaBon from Flo2Cash of successful payment) – processes top up and sends standard top up confirmaBon messages

AUTO TOP UP

ME2U STEP-‐1 STEP-‐2 STEP-‐3 STEP-‐4

Developing DifferenBators – FB TOP UP

Developing DifferenBators – ONLINE POSTPAY CONVERSION

Business Process IntegraBon – Sample Flow

Component Architecture

External IntegraBon Layer

Internal IntegraBon Layer

Business Process Layer

Business Services

Delivery Channels Delivery Channels Delivery Channels

Business Data

2Degrees Customers Internal Business

Users

Internal Techn

ical

Users

SoluBon Architecture

External IntegraBon Layer

Internal IntegraBon Layer

Business Process Layer

Delivery Channels Delivery Channels Delivery Channels

Business Data

2Degrees Customers Internal Business

Users

Internal Techn

ical

Users

20

WSO2 IntegraBon Overview

Deployment Architecture

Architectural Summary

Before Now -  Full SOA ApplicaBon Stack

-  Architecture build as per Best PracBces

-  Removing complexity from Apps and building it into BPS

-  Full TransacBon monitoring

-  Content Switch used for clustering and load balancing

-  Development and Deployments streamlined (Carbon Studio)

-  Complex processes delivered via BPS and simple via ESB

-  ESB and DSS ApplicaBons

-  Architecture build as needed – home-‐grown

-  Limited transacBon monitoring (debug logs)

-  Linux LVS used for clustering and load balancing

-  Development and Deployments manual

-  Complex composite services deliver Business processes via ESB proxies and sequences.

Project Challenges

-  Huge scope -  Fluid business requirements -  Aggressive Bmeframes -  Lack of familiarity/experBse with the WSO2 stack -  Lack of enough skilled WSO2 resources in nz -  Ensure smooth handover to operaBons

Results

-  Hired good middleware developers & administrators -  Went through WSO2 training (quickstart & webinar) – both

project & operaBons resources -  Divided the scope in discrete work packets -  Tried to use out-‐of-‐box features as much as possible -  Implemented simpler requirements first -  Consulted WSO2 -  Hired external auditors for security & performance tesBng -  Managed to deliver all the workflows & applicaBons on

schedule

Vision & Future IniBaBves -  Introduce Governance and Business AcBvity Monitor

-  IdenBfy the scalability needs by doing a capacity planning -  Re-‐architect by idenBfing the common shared services

-  ConBnued Focus on InnovaBon & DifferenBators -  Offer comprehensive customer lifecycle through Online channels

-  Create Web Service wrappers for all key Telco Systems/Network Elements to enable flexibility in design using the SOA paradigm

-  UBlize smart technology to give rapid response to compeBBon

-  Increased porLolio of services offered through Social Networking tools

-  Facilitate innovaBve models like SDP and external partner collaboraBon and shape the 2degrees SOA stack accordingly

More Info

§  Corporate website: hKp://wso2.com

§  Developer portal: hKp://wso2.org

§  Business development team: [email protected]

§  2degreesmobile

§  Website : h\p://www.2degreesmobile.co.nz/

Upcoming Webinars

•  Enterprise Use Case Webinar -‐ Applica9on Development Using the WSO2 Developer Studio -‐ Thursday, 24th May 2012

•  WSO2 Product Release Webinar: Introducing Jaggery, the Server-‐Side JavaScript Framework for Composing Web Apps -‐ Thursday, 31st May 2012

•  WSO2 & eBay Case Study -‐ How eBay Uses the Open Source WSO2 ESB to Process Over 1 Billion Transac9ons Per Day -‐ Thursday, 7th June 2012

•  WSO2 Advantage Webinar: Apply API Governance to RESTful Service APIs using WSO2 Governance Registry and WSO2 API Manager -‐ Thursday, 14th June 2012

5/17/12 27

28

lean . enterprise . middleware