Journey of Migration from Legacy ESB to Modern WSO2 ESB Platform

Ratnavel SundaramurthiAspire Systems Inc.,

Michael Enos TechSoup Global

Joint Presentation

TechSoup’s Impact

in technology products and grants employed by NGOs for the greater good

saved, on average, by nonprofits that use TechSoup’s resources

corporate and foundation partners connected with the causes and

communities they care about

annual visits to our websites

newsletter subscribers who want practical IT knowledge

$7.6B

$17,400

100+

7.4M

700,000

1M

▪ TechSoup Members Worldwide▪ Over a quarter million in the U.S.

Together, we build a stronger, more resilient civil society.

TechSoup’s Programs

TechSoup’s Programs

4

GuideStar International

Provides NGOs with technology, products, services, and education at low

or no cost.

5

Caravan Studios

6

NetSquared

1

TechSoup.org

2

NGOsource

3

Data Services

Simplifies international giving for grantmakers and grantees.

Connects philanthropy programs with validated NGOs around the world.

Provides an information system for NGO reporting and transparency.

Creates apps that help communities solve critical problems.

Builds local communities for people working in social good technology.

Aspire Systems Impact

Customers

2000+

150+

Great Placeto Work7Times

Center of Excellence 4

GlobalLocations6

Employees

Agenda

Why Migrate at all?1

What we needed?2

Challenges Identified3

Our journey4

Solution ▪ Architecture ▪ Deployment

5

Benefits of the project6

The Time was Right

Why Migrate at all?

Business Continuity

Business Scalability

▪ New ArchitecturesMoney?

▪For some “its NOT the primary reason”▪For others “Not THE Reason”▪For few “Its THE Reason”

Support

Business Problem

Goal: Align Technical Strategy with

Business Strategy

Driver: Shift of technology strategy

Transformation: Legacy middleware solution not meeting needs of business/tech strategy

▪ Bring products/services to market faster in our tech-for-good marketplace

▪ Reduce technical debt/costs▪ Improve

performance/availability/scalability▪ Sustainability

▪ Cloud infrastructure ▪ SOA/ MSA▪ Dev-Ops

▪ Upgrading current solution cost-prohibitive

▪ Traditional on-premise system not in alignment with tech strategy

What we needed?

3

Retiring unused web services

7

Faster time to value

6

Quick time to market

5

Implement better versioning strategy for services

4

Implement content based routing

2

Consolidation of web services

1

Leverage Existing Systems

#OurJourney

The landscape

Acceptance criteria

▪ Migration needs to be seamless▪ Consumers should only change the

endpoint URL

Project scope

▪ Analyze, Design, Migrate, Test & deploy 27 web services

Project timeline

▪ 3 months

Legacy ESB platform used

▪ Oracle Service Bus▪ SQL Server

▪ Develop regression tests▪ Code Review▪ Unit test

▪ Migrate Oracle Service bus to AURAS(WSO2 ESB) services

▪ Salvage and reuse possible components

▪ Migrate existing date to new data model

Mig

rati

on

Test

ing

Mig

rati

on

▪ Independent (Alpha) test▪ Stress test

▪ Functional test against business rules

▪ Beta Testing (UAT)

▪ Parallel Operations▪ Performance Assessment▪ Assess usability▪ Deploy migrated servicesD

eplo

ymen

t

Val

idat

ion

Acc

epta

nce

Migration Strategy

▪ Finalize inventory▪ Define core functions▪ Rectify migration inventory

eliminating unused functions

▪ Identify key constraints▪ Identify Migration

Deliverables▪ Develop Project PlanP

lan

nin

g

Ass

essm

ent

Dis

cove

ry

Design

▪ Identify application architecture

▪ Identify possible reusable components

▪ Identify key business rules

Rev

erse

En

gin

eeri

ng

▪ Develop new data model▪ Develop new orchestration

services ▪ Verify design feasibilityD

etai

led

Des

ign

Discovery Process

▪ Discovery Phase Kickoff Meeting

▪ Assessment approach review

▪ Identification of key Business and IT Stakeholders

▪ Interviewing key Business and IT Stakeholders

▪ Discuss with IT Managers & Architects

▪ Story Drafting

▪ Gather Business, IT Documents/References

▪ Review Existing Internal & External Services

▪ Review Existing Data Mapping / Models

▪ Review Business Processes▪ Review Non Functional

Requirements▪ Consolidate Document

References▪ Final check with Business &

IT leaders

▪ Review Interview References / Story

▪ Consolidate Document & Interview References

▪ Review Evidences▪ Compare with Industry

practices / Standards▪ Document Findings and

Recommendations▪ Prepare High Level

Architecture for the proposed ESB specification

▪ Prepare Project Plan

▪ Prepare Detailed Assessment Reports

▪ Review the Reports and Deliverables with Key Stakeholders

▪ Corrections▪ Publish the Final

Deliverables▪ Discuss action items with

Enterprise leaders▪ Closure Meeting

Interviews

Phase 1 Phase 2 Phase 3 Phase 4

System Reviews

Analysis / Documentation

Deliverables Review

Challenges Identified

Existing Middleware solution used Custom .Net components

Lack of versioning with services

Lack of documentationEach consumer used a version of service

Consolidating multiple versions of services with being backward

compatible. Some services had 6 versions in existence and actively used

Support for consumers with different technologies (PHP 5.3, PHP 5.6, .Net Framework 3.0, .Net Framework 4 & Java)

Handling exceptions, tracking of transactions and resubmitting requests

was a challenge

Deployment was a challenge

Technology used

Apache Active MQ 5.13.x

Microsoft azure

Ansible

XSLT

SQL Server

AURAS Gen V 2.0(Framework built on WSO2 ESB)

Jenkins

Customer’s Integration PlatformIntegration Platformwith customizations specific to the customer

AURAS-Gen

Pre-built best practice Services

AURAS-Omni

Omni Channel Services (NRF-ARTS)

ESB + API

Inner core of theIntegration Platform

What is AURAS?

And the

winner is…

Which one

to choose?

I Need an

Integration Tool,

I see too many

Why WSO2?

Its 100 % Open Source

Connect Anything to Anything

Support for multiple transports, formats & protocols

Cloud ReadyIts Lightweight, Developer-Friendly, and Easy Deployment

For us WSO2 ESB proved to be a successful and efficient COTS with great features

WSO2 Enterprise Service Bus

AURAS-Gen

Business App Services Process Services Information Services

User manager Services Utility Services Payment Services

E commerce Services Order Management Services Partner Services

Gateway

Qu

eue

Man

ager

CRM ERP Applications SaaS Database

Online Shopping

E commerce Social MediaPartner

ApplicationsApplications SaaS

TSG Architecture

TSG – Hosted Network Architecture

Existing D

ata C

enter

Internet

Load Balancer

Enterprise Service Bus

VPN

VPN

Enterprise Service Bus

Enterprise Service BusEnterprise Service Bus

Enterprise Service Bus

TSG – CI\CD Architecture

1

Launch Maven

Build TestingPacking Archiving

CONFIGCONFIG

Development

CONFIGCONFIG

QA

CONFIGCONFIG

Staging

CONFIGCONFIG

Production

2

3 4

Build Process

Pull the Code

Code Change

Commit Code

CONTINUOUS INTEGRATION

CONTINUOUS DEPLOYMENT

Benefits

Improved business agility allowing the company to adapt swiftly and efficiently to emerging requirements

Services were consolidated and better versioning

strategy implemented

Maintenance of existing infrastructure became easier

Processes are automated without

manual intervention

Extensive Error handling comes with the solution to include any after error process

Services were modularized based on

the operation they perform

Thank You!http://www.auras.aspiresys.com