WSO2Con EU 2015: Case Study – Digital Transformation: To Monetise Business by Building Elastic API Eco Systems In a world where Google & Amazon are battling it out for “Same Day Delivery Service Models”, an (r)e-tailer can either get their delivery strategy right or lose customers. This session will present how WSO2 helped one of the largest same day delivery companies to expand and transform their existing delivery business by creating an API platform for the (r)e-tailer. The APIs opened a new channel enabling increased engagement with their customers. They were also able to provide a multi-tenanted capability to each (r)e-tailer, keeping their data separate along with custom security mechanisms tailored for each one of the (r)e-tailer needs. To top things up, the entire WSO2 platform is hosted on the cloud, enabling easy scale for the spikes during sales seasons, so that you as a customer get your delivery in time for the special occasion. Presenter: Ashish Mital Principal Architect Aditi Technologies

1. Digital
Transforma/on:
Connected
API
ecosystems
Ashish
Mital
Principal
Architect-­‐
(
OpenSource
Prac/ce)
Adi/
+
SymphonyTeleca
(A
Division
of
Harman)

2. Aditi + SymphonyTeleca –What we
do?
Drive unique, intelligent connected experiences
leveraging the convergence of
Design, Device, Analytics & Cloud

3. Uniquely connected experiences
leveraging … - How ?
… delivering time to market acceleration
Connected
Device
Connected
User Exp.
Connected
Data
Connected
Platform
Member of
Open Handset
Alliance
Android
Device
Certification
Partner
Only Services
Company in
the OAA
Best IoT
partner
Windows
Azure
Partner of
the Year

4. …at a Global Scale
US
ARGENTINA
GERMANY
POLAND
UK
SWEDEN
FINLAND
RUSSIA
INDIA
CHINA
KOREA
JAPAN

5. HOW we helped build
CONNECTED API ecosystem
for 1 of our CUSTOMER using
WSO2

6. Ask – Expose Business features as
API
Build a platform, an eco-system - tapping new channels for
customer engagement and revenue growth.
Business features
as API Platform

7. Involves building APIs that
are…
APIs
Discov
erable
Int. &
contex
tual
Adapt-
able
Scale
Device
&
Format
Perfor
mance
SLA
Availa
ble
Secur
e
Gover
ned
Multi-
tenant

8. Solution components
API Manager + ESB
• API Manager -publish,
subscribe, collaborate
• Workflow for signup -
Sandbox & Production
• Micro Services-based
architecture
• ESB – support
transformation &
orchestration
Scale + DevOps
Cloud & NoSQL
• AWS based deployment
• Multi zone & region
availability
• High speed Cassandra
NoSQL database
• DevOps to manage the
scale
Security –
Identity Server
• Support for SAML,
OAuth, JWT – Federated
Identity
• XACML & RBAC
Authorisation
• Multi-tenancy

9. Platform evaluation – Why WSO2?
Evaluation of a number of platforms based on below tenets
Capability
vs.
Requirement
matrix
Formats &
Protocols
Connectors
Design & run
Time
Governance
Cohesive
Platform
suite
Familiarity to
Java/J2EE
Resource
availability
Cloud vision Support &
Documenta-
tion

10. IdentityMgmt.
User
Profiles
Federated
Authn.
Roles
XACML
Key
Mgmt.
SSOConsumer
Landscape
OAUTH SAMLOpenID
API
Management
Throttling Security Collaboratio
n
Subscriptio
n
API
Catalog
AWS
Common
Boiler
Plate
-­‐
Accelerators
Routing Xformation Messaging Adaptors Entitlement
Business
Components
ERP/CRM
Legacy
Apps
Pmnt.
Gtwy
3rd
Party
AWS
Retailer Orders Voucher Subscript
ions
Timeslot
Retailer Orders Voucher Subscript
ions
Timeslot
Operational
Management
• Logging
• Exception
Handling
• SLA
Mgmt.
• Monitoring
• Administration
NoSQL
Enterprise
Datastore
AWS
AWSAWSAWSAWSAWS
Logical Architecture
Micro
services
NoSQL
Common
Functionality
Open APIs
Touch
points
Security
Resilient
Heterogeneous
Scalable
Replaceable
Boiler-
plate

11. Identity & Access Mgmt. Needs
Professional
Identity
Intranet
Server Server
Server
Social
Identity
Multiple
profiles
Multiple
devices
Anywhere
presence
Multiple
Protocols
APIs

12. Solution - Identity as a Shared
Asset
Single Sign In/Out SAML
Federated Identity SAML/Google/FB
API access based on
roles
OAuth Tokens with
roles + JwT
Authorisation
XACML Entitlement
Filter
Project Needs Identity Server

13. Scale that requires - DevOps
• Parallel feature development streams
• 6 deployment environments across
streams
• 4+ deployments/day (across DEV, UAT..)
• Fail fast - Continuous Integration/Delivery
• 50 + VMs on cloud required Configuration
Management
• Monitoring (APM, Browser, Hardware)
Emulate Production
Environment for Development
and Testing
Embrace Agile to ship releases
in weeks
Accelerated Deployment using
tools like Chef, Puppet
Monitor and Capture the right
metrics using tools such as
JIRA, TFS, VersionOne
Establish an open channel of
communication
Stable Build with Continuous
Delivery and Integration using
tools such as Bamboo, Hudson

14. DevOps – Our implementation
• Configuration Mgmt. on cloud along with cloud former
• Spinning and managing VMs, different node roles
• Each micro service can be built independently
• Hierarchical pom.xml for better control
• Automated Junit coverage
• Jenkins selenium plugin using xvfb on Linux
• 1 click build & packaging providing CI & CD
• Pre-post build steps for checkout & copying artifacts
• New Relic & Nagios to monitor server hardware
• Application performance & browser metrics.

15. Externally Connected
(Customers and Partners)
Result - Connected Experience
Delivered !
Connected Devices Connected Data
Connected
Platforms
Connected UX
Internally Connected
(Enterprise)
API-centric SOA
Big Data/ Complex
Event Processing
Agile Delivery and
DevOps
Mobile First/ Cloud
First

16. Thank
You