This deck will cover the problem with running systems in isolation. how you can move away from isolated systems, an Introduction to the concept of services oriented architecture and integration hub, the benefits of sharing information and services, and will introduce the concept of API Management.

1. Digital Transformation: Breaking Down
Boundaries for Greater Connectivity
Executive Session

2. WSO2 At-A-Glance
2
$36m Sales in
2018
53% YoY
growth
500+
Customers,
200 New
Customers
in 2018
Open
Source
Founded 2005,
Backed by
Cisco and Toba
Capital
Colombo,
London,
Mountain View,
New York, São
Paulo, Sydney
500+
Employees
(300 Engineers)

3. 3
#1
6th
Open Source Integration Vendor
Largest Apache Committer
Largest Open Source Vendor
7th
WSO2: Helping Digitally Driven Organizations
Become Integration Agile

4. “Strong Performer for Hybrid
Integration”
- The Forrester Wave™: Hybrid Integration for
Enterprises, Q4 2016 report, published Nov. 18, 2016
“Strong Performer for API
Management Solutions”
- The Forrester Wave™: API Management Solutions, Q4
2016 report, published November 14, 2016.
“Strong Performer for Big Data
Streaming Analytics”
- The Forrester Wave™: Big Data Streaming Analytics,
Q1 2016 report1, published March 30, 2016.
“Visionary”
- Gartner Cool Vendors in Internet of Things Analytics,
2016 report, published May 11, 2016.
- Gartner Magic Quadrant for Full Life Cycle API
Management, published 2018
“Cool Vendor”
4

5. Flagship Customer Examples
Applied uses across every industry and geography
Financial Healthcare Governments Education Telecom Retail TechnologyTransport
5

6. ● Problems with running systems in isolation.
● How you can move away from isolated systems.
● Introduction to the concept of services oriented
architecture and integration hub.
● Benefits of sharing information and services.
● Introduction on the concept of API Management.
● Demo.
Agenda

7. Evolution Of Applications
Disaggregated architectures drive 50 billion endpoints to grow >1 trillion
CONSUMER DEMAND
SUPPLIERS DISAGGREGATE ARCHITECTURE TO MEET DEMAND
1
10
102
103
105
109
MONOLITHIC
BUSINESS APP
ENTERPRISE
APPS
DEPARTME
NTAL APPS
SAAS APPS
PUBLIC /
PRIVATE APIS
1970s
|
MAINFRAME
1980s
|
IT
AWAKENING
1990s
|
INTERNET
2000s
|
MOBILE
2010s
|
IoT/AI
2020+
|
DIGITAL NATIVE
SERVERLESS &
MICROSERVICES

8. 8
Half of All Development Will Be Integration
Consider that today’s 50mn endpoints will soon grow to 1T

9. Isolated Systems (Silos)
• Large (monolithic)
system.
• Isolated and independent.
• Build to solve the needs
of a specific segment.
• No standard way to
communicate with other
systems.

10. Why Do Organizations Run Systems in Isolation
• Control and security.
• Effort required to open up systems for other consumers.
• Systems built to run in isolation.
• Lack of business requirement to share access.
• Low emphasis on innovation and building new
capabilities.

11. Problems in Running Systems in Isolation
• Too much paperwork.
• Difficult to integrate with other systems.
• Duplication of processes.
• Lack of reusability.
• Expensive to maintain.
• Less scalable.
• Slow to adopt change.
• Doesn't suit modern IT landscape

12. Journey to Move Away from Isolated Systems

13. Journey to Move Away from Isolated Systems
Service Oriented Architecture

14. What is Service Oriented Architecture (SOA)
• Communicate via standard communication methods.
• Product, vendor, technology independent.
• Services can operate independently.
• Services share contract, not language specific classes.
• Policy driven, pre agreed contracts. No paper work
required.

15. What is Service Oriented Architecture (SOA)

16. What is Service Oriented Architecture (SOA)

17. What is Service Oriented Architecture (SOA)

18. Why is this Beneficial?
• Re-usable.
• Flexible.
• Easy to maintain.
• Scalable.
• Better services for your citizens.

19. But, How Does This Look in Real World?
• Complex integration.
• Security and access
management concerns.
• Reliability in
communication.
• Monitoring usage.

20. How Do We Address These ConcernsT
• Minimize integration through an integration hub.
• Standardize integration points.
• Easy way to find out what services are available.
• Security and access control.
• Ensure messages are delivered correctly (no loss in
delivery).
• Analyzing usage of components.

21. How Do We Manage The Complexity

22. How Do We Manage The Complexity

23. How Does Communication Take Place?
• Communication via APIs.
• Contract shared
beforehand.
• Other agencies to access
APIs via a standard, secure
way.
• Usage can be monitored
and controlled.

24. Business Benefits
• Cut down duplication of effort and encourage
reusability.
• Reduce time to market when creating new services.
• Better integration with the overall ecosystem.
• Control way of sharing access to other agencies who
wants to consume services.
• Better product delivery and satisfaction of employees.

25. Connect Anything to Anything

26. Orchestrate Between Services

27. Control Access
Policy enforcement

28. Reduce Business Impact

29. Data as a Service
• Expose data as a service to consume as standard web
services.
• Federate data from multiple sources (response to a
request would contain data from multiple sources).
• Bulk updation of data.
• Data security and filtering.
• Data enrichment with other services.

30. Data as a Service

31. API Management

32. API Management
• Gateway thru which services are exposed to outside.
• Acts as a gatekeeper to ensure only legitimate users
can access services.
• Controls “how”, “who” and “when” data is accessed.
• Control the rate at which data is consumed.
• Clear way of managing versions and lifecycle of a
service.
• Easy way to discover services that available.

33. API Portal

34. How Does It All Fit Together

35. Demo

36. Scenario
• Royal Monetary Authority (RMA) to provide a service to
check the credit rating of a citizen.
• RMA is required connects to multiple systems to gather
required information of the citizen.
• RMA will calculate the credit score based on these
information collected.
• RMA offers this service as an API for other agencies to
access (one stop shop).

37. Scenario

38. WSO2 Presence In The
Banking Industry
38

39. Banking Industry
• Majority of customers are from Banking, Finance and
Insurance Industry.
• Fidelity Investment, BNY Mellon, Deutsche Bank,
American Express, Standard Chartered ….
• Pre-built connectors for banking systems.
• Open Banking solution for banks.

40. Success Stories
40

42. 42

43. 43

44. THANK YOU
wso2.com