[WSO2 Integration Summit Stuttgart 2019] Role of Integration in an API Driven World

INTEGRATION SUMMIT 2019
Role of Integration In API Driven
World
Asitha Nanayakkara
Technical Lead, Integration team
INTEGRATION

Story of SuperCity

Challenge from Digital Competition

New Strategy
Reuse existing systems
Cost Savings
Faster time to market
Work with legacy
backend systems
Room for future
expansions
API Management solution along with some broad integration capabilities

SuperCity API Initiative
API
Existing System
Mobile
App
Website

API Driven Development

Why APIs ?
● APIs are a key enabler of digital enterprise
● APIs acts as gateways to enterprise digital asserts
● Allows the enterprise to build new digital consumer experiences within
accelerated time frame
● They open up new revenue channels and expand existing revenue
channels
● APIs enable the enterprise to cater for future expansions

Code ﬁrst design
Code First vs API First Design
Back-end
Team
ImpI 1
API
2
Client
A
Client
B
...
SDK SDK ...
3
Front-end
Teams
API ﬁrst design
Front-end
Teams
Back-end
Team
API API API
Mock Mock Mock 1
Client
A
Client
B
...
SDK SDK ...
ImpI 2
2
ImpI ImpI
Data Services

API Façade
IoT
Mobile
Apps
Web
API Gateway
API Façade
DatabaseLegacy System
Content
Management
CRM/HR/Inventory
Systems
SaaS

API Façade
System 1
API 1
System 2
API 2
Composite API
System APIs
Orchestration APIs

Orchestration APIs
Invoke
Policy / discovery
Enrich Publish DB write Transform Update
Policy
Orchestration API
CRM
API1 Queue
DB
REST
API

API Façade
IoT
Mobile
Apps
Web
API Gateway
API Façade
DatabaseLegacy System
Content
Management
CRM/HR/Inventory
Systems
SaaS
API A API B
Orchestration API
Orchestration APIs
System System

SuperCity’s Digital Story

Building the API’s
Price
Update
System
Inventory
System
Reservation
System
PoS
System
Store 1
Store 2
Store 3
Mobile App
Website
API
API
Delivery System
API
Payment System
API
API
API

Building the API’s
Price
Update
System
Inventory
System
Reservation
System
PoS
System
Store 1
Store 2
Store 3
Mobile App
Website
API
Delivery System
API
Payment System
API
Managed API
API
API
API

Types of digital assets in enterprises
● Application silos that hold key business capabilities of the enterprise
● Enterprise SaaS applications
● Enterprise Data stored in various storage mechanisms including RDBMS,
Files, Spreadsheets, CSV ﬁles ...
● Applications that execute the process ﬂows in the enterprise
● Systems based on proprietary protocols and data formats

Key integration capabilities
● API and Service Hosting
● Orchestration of services and apis
● Routing
● Transformations
● Protocol switching and ability to process different data formats
● Parallel processing

Integration Strategy
• Discover the ecosystems and Application silos
• Understand the data
• Understand the capabilities
• Identify the possible integration points for each system
• API enable the identiﬁed systems
• Implement the integration logic

WSO2 Enterprise Integrator

A Hybrid Integration Platform
Connectivity / Integration: anything-to-anything
WSO2 EIConnectors
Web services
APIs
Filesystems
Messaging systems
Business
Applications
Partners’ systems
Data
Supporting Standards
• HTTP(S)
• JMS, AMQP, MQ
• Websockets
• VFS
• FIX, HL7
• JSON, SOAP
• XSLT, XPATH, Smooks
• JDBC, CSV, NO-SQL
• OAuth, XACML, WS-Sec

Enterprise Integrator Capabilities

API Integration - Integrator Profile
A lightweight, high performance integration runtime
• Comprehensive REST, SOAP, and WS-* support
• Support for File, Data, Messaging based integrations
• SAP, FIX, and HL7 - Domain specific solutions
• Configuration driven
• Extensible and Scalable
• 100% coverage of all EI patterns

Data Integration - Integrator Proﬁle
Building service abstractions on top of disparate data sources
SQL
SOAP/REST/OData
XML/JSON
Integrator Runtime
WSO2 EI

Business Processes - BPS Profile
Processes/Workflows with BPMN, BPEL, Human Tasks
Application α
Application β
Defined processes and workflows
which may also consist of human
tasks
Business Process Execution
as a Service
WSO2 EI
Application N
Process Initiation
Results/Decisions

Micro Integrator
• Can be to used to create composite services using atomic services
• Separate distribution that can be used in a cloud native environment
• Users can use the same EI tooling to create artifacts
• Deploy few composite integration services per micro integration
• Command line tool for management tasks
• Fast startup time (5s)
• Small distribution size of 150 mb
• K8S Integration
https://github.com/wso2/micro-integrator

Micro-integrations
Consumer 1
API Service P API Service Q API Service R API Service S
Consumers
Consumer 2 Consumer 3
μ Service A
Proprietary &
Legacy
Systems
Web API /
SaaS
API Services/
Edge Services
Composite Service/
Integration Services
Core Services/
Atomic Services μ Service I
μ Service H
μ Service J
μ Service E
μ Service C
μ Service D
μ Service G
μ Service B
μ Service F
API
Management

WSO2 EI Graphical Tooling
• Drag and Drop Visual Editor
• Develop, Deploy, Test, Debug
capabilities from the editor
• Build in micro Integrator runtime for
testing and debugging
• Export artifacts as a docker image
with micro integration
• Integration templates for rapid
development

Integration Analytics
Dashboards for Transaction Analytics and Monitoring
Overall setup
• Overall Throughput (in TPS)
• Overall Message Count
APIs, proxies, endpoints speciﬁc
• Request Count
• Message Count
• Message Latency
• Explore Messages
• Explore Message Flows

Other Analytics Integrations
• ELK Stack
• Prometheus

Continuous Integration and Continuous Delivery
Continuous Integration
Server
Source Control
System
WSO2 EI
WSO2 EI
Environment 1
WSO2 EI
WSO2 EI
Environment 2
Continuous Test Server
Integration
artifacts
IDE IDEIDE

Solving the Integration
Requirements with WSO2 EI

Integration with Systems that Talk in Standard
Protocols
Support for a wide range of
standard protocols
• HTTP/HTTPS
• JMS
• AMQP
• FTP/SFTP/FTPS/SMB
• SMTP/IMAP
• MQTT
• KAFKA
• And many more
SMTP
HTTP
JMS
FTP
Websocket

Integration with Systems that Talk in Standard
Protocols
HTTP/API
Public Private Organization
Existing
System
FTP

Integration with Systems that Talk in
Non-standard/ Proprietary Protocols
• Built in support for well-known proprietary protocols
E.g. SAP
• Easy to extend the functionality to introduce new protocols
HTTP/API
Public Private Organization
Existing
System
Non Standard
Protocol
Connector

Integration with Files-based Systems
● WSO2 Enterprise Integrator supports a wide range of file transferring
protocols such as FTP, SFTP, FTPS, and SMB
○ Listen to a location, pick files, and invoke a web API using the content of the
files
File HTTP
Web API
Invocation
Existing Legacy
System

Integration with Systems that Use Databases
Expose databases or other data sources as services
HTTP

Extension Points
• Script mediator
• Connectors
• Custom/Class mediators
• API handlers
• Custom tasks
• Custom inbound endpoints
• Custom XPath functions
• Message builders and formatters
• Transport listeners and senders
• Custom message
stores/processors

Conclusion
● Why API Driven integrations are important
● API and Integration strategy and approaches
● WSO2 Integration suite functionality to support API driven Integration
● How to successfully implement API driven Integration

THANK YOU
wso2.com

Questions?

[WSO2 Integration Summit Stuttgart 2019] Role of Integration in an API Driven World

Recommended

More Related Content

What's hot (18)

Similar to [WSO2 Integration Summit Stuttgart 2019] Role of Integration in an API Driven World (20)

More from WSO2 (20)

Recently uploaded (20)

[WSO2 Integration Summit Stuttgart 2019] Role of Integration in an API Driven World