One of the burdens modern integration developers face is the disconnectivity between design, development, debugging, testing, and deploying integrations. WSO2 Enterprise Integrator provides a rich developer experience with all the tools you need to construct complex enterprise integrations. Learn how WSO2 Enterprise Integrator gives you a connected developer experience when building an enterprise application.
This deck will explore how to simplify the integration of services with integrated middleware, creating a unified API management platform for a connected business, and a demonstration of an agile platform for a connected business.
Making a Connected Integration Developer Experience using WSO2 Enterprise Integrator
1. Prabushi Samarakoon | Rosen Silva
Integration Team
1
Making a Connected Integration
Developer Experience using WSO2
Enterprise Integrator
2. Agenda
• Requirement of agility for business platforms
• Burden of disconnected integration experience
• WSO2 EI approaches to cater integrated developer experience
• Demonstration on building a CI/CD pipeline with WSO2 EI
2
4. Why Agile Approaches?
Quality & performance
● Best practices lead to
high quality and high
performance in the
long run
Adaptability
● Rapid respond to
changes
● Remain in industry
competition
Flexibility
● Incremental iterations
● Communication
oriented
● Transparent
5. ● Identifying the requirement of an agile approach can be vague.
● It can result high costs with uncertain future.
● Transparent communication can consume more time for smaller tasks.
● Disconnected developer experience can cause increased overhead with its incremental
iterations.
Challenges with agile methods
6. Enterprise Integrator
WSO2 Enterprise Integrator
● (SOA) Service Oriented
Architecture
● A comprehensive
integration solution
● (MSA) Microservices
Architecture
● Container native
● Improved performance
Micro Integrator
● Developer tools to
implement integration
solutions
Integration Studio
8. The ‘Coffee-Shop’ has a legacy SOAP service, which manages orders.
It wants to expose some of the capabilities of this ‘Order Management
System’ via APIs.
Following are the services required to be implemented;
1. An API to place an order
- API needs to call the backend legacy system to process the order
- API needs to create a file with the order details for printing purposes
2. An API to cancel an order
- API needs to call the backend legacy system to cancel the order
Scenario
9. Design
1 New order
request
2
Create file
Process order
Order status
response
Cancel order
Cancel order
request
Cancelled order
response
Cancellation success
response
3
4
Order success
response5
1
4
2
3
Legacy Order
Management
System
14. Deploy in an added or a remotely connected server, or in embedded MI
Deploy
Host on Integration Cloud
15. CI/CD Pipeline
Integration Studio
Implement mediation
artifacts and commit
changes to the source
repository.
Source Repository
Maintain artifacts
developed by team
members.
Continuous
Integration Tool
Retrieve artifacts from
the source repository,
and build against the test
suite.
After verifying the
functionality, artifacts are
committed to the
production environment.
Production
Environment
Provide services with the
newest artifact changes.
17. Design
1 New order
request
2
Create file
Process order
Order status
response
Cancel order
Cancel order
request
Cancelled order
response
Cancellation success
response
3
4
Order success
response5
1
4
2
3
Legacy Order
Management
System
19. New Requirement
1 New order
request
2
Create file
Process order
Order status
response
Cancel order
Cancel order
request
Cancelled order
response
Cancellation success
response
3
4Order success
response5
1
4
2
3
Legacy Order
Management
System
Update order
request
Update success
response
Update order
Updated order
response
1
4
2
3
20. Summary
• It is important to have an automated system to cater
requirements in an agile business platform.
• WSO2 Enterprise Integrator can be used to address any agile
business integration solutions with a connected developer
experience.