The Role of Enterprise Integration in Digital Transformation

Kasun Indrasiri Director – Integration TechnologyMarch 2017

2

Agenda

Digital Transformation and Integration Centralized Integration Future Integration needs Microservices and Integration Decentralized Integration – Micro-Integration State of the art integration middleware WSO2’s Next generation integration platform with Ballerina

3

Digital Transformation and Enterprise Integration

DT in a nutshell o Evolving Business Modelso Focus on customer experience o Optimize Operation

Brown-field reality requires integrationo Hence Enterprise Integration is a key step

towards Digital Transformation.

4

State of Integration Technologies Landscape

Application and data integration technologies are moving to a dynamic space – Cloud, Mobile, APIs, IoT, Convergence of Data and Application Integration

5

Centralized Integration

A central integration middleware that connects application, services and data

Conventional SOA/ESB approach Legacy systems to cloud services connected with services, data,

messages and processes.

6

Centralized Integration WSO2 Enterprise Integrator 6.0

Drag picture to placeholder or click icon to add

7

Centralized Integration

WSO2 Enterprise Integrator 6.0 – Runtime Structure o ESB and DSS as a single runtimeo Message Broker o Business Process Servero Application Servero Analytics (primarily ESB analytics)

8

Can Conventional Integration Middleware survive?

Drastic changes in modern Enterprise Integration needs.

Not compatible with new architectural paradigms (e.g. Container Architecture, Microservices)

Almost all integration middleware solution more or less offer the same set of functionalities for a decade or so.

9

Future Integration needs

Microservices and ESB/Integration Middleware o Increasing adaptation of Microservices

Architecture o Microservices do not encourage the conventional

centralized integration middleware. o Integration middleware solutions are not container

native.

10

Microservices architecture rejects ESB?

Smart endpoints and Dumb pipes. o No ESB! o All the business logic and routing logic should be

moved to the endpoints.

11

Microservices architecture rejects ESB?

Smart endpoints and Dumb pipes => Point to point Integration

12

Microservices and Enterprise Integration – In Practice

Netflix API “The Netflix API is the

“front door” to the Netflix ecosystem of microservices. As requests come from devices, the API provides the logic of composing calls to all services that are required to construct a response.”Source : http//techblog.netflix.com/2016/08/engineering-trade-offs-and-netflix-api.html

13

Microservices and Enterprise Integration – In Practice

Uber Uber uses ‘Edge Services’

which are exposed to the external client/mobile applications and the service orchestration logic is burnt into the edge service.

Source : https://www.infoq.com/presentations/uber-darwin

14

Microservices and Enterprise Integration – In Practice

Paypal The API façade layer

exposes Paypal business functionalities to various internal and external client applications and orchestration logic resides at that layer.

Source : https://www.infoq.com/presentations/paypal-api-evolution

15

Microservices and Enterprise Integration – In Practice

Microservices still requires an integration layer that can implement service/API orchestrations and connect to any other external system.

Use monolithic centralized integration middleware? – NO

Need of ‘Decentralized Integration Middleware’

16

Decentralized Integration

No centralized integration bus/ESB. Build independent integration scenarios using

integration framework -> Micro-Integrations/Integration Microservices

17

Micro-Integration/Integration Microservices

Build a specific integration scenario and run that scenario independently with a light-weight integration framework.

One integration scenario per each runtime. Runtime is extremely lightweight fully container

native. Develop, deploy and scale each integration

scenarios Independently.

18

Micro-integration

Integrating Microservices

19

Micro-integration

Integrating applications, services and data.

20

Micro-integration

Integrating Microservices and other conventional applications

21

Micro-integration

Scaling Micro-integrations 5 – Instances

2 – Instances

10 – Instances

Types of Micro-integration

23

Future Integration needs

Growth and diversity of Integration needs o APIs and SaaSo Internet of Things o On-premise applications

• B2B, Proprietary, Legacy systems

24

Future Integration needs

Agility and ease of Integrationo Minimum integration skills and operational

overhead. o Customize existing integrations rapidly. o Visual modeling, debugging, trouble shooting o Analytics – Statistics, message tracing o Error handling. o Streamlined development life cycle.

25

Future Integration needs

Orchestration – Implementing complex orchestration logics o Proliferation of services, APIs and applications to integrate.o Complexity of the orchestration logic increaseso Need a simple and agile development of orchestration logic

– Visual modeling tools.

26

Future Integration needs

Orchestration – Implementing complex orchestration logics o Use case : Netflix API: Single API call to nested,

conditional, parallel execution of multiple backend network.

27

Future Integration needs

Integrating applications, services, data, APIs and identityo There’s a broad integration challenge than the traditional

ESB related integration. o Integration Server, Data Integration, Identity Bus, API

GW/Composition

28

Future Integration needs

Performance o No of transactions and latency o Ever increasing growth of traffic.

Source : http://blog.mailchimp.com/10m-api-calls-per-day-more/

29

Future Integration needs

Performance o No of transactions and latency per containero Startup Timeo Memory foot printo Distribution size o Average CPU consumption, Load Average

30

Future Integration needs

Scalability o Container based scaling o Scaling based on the integration solution

o E.g : Ability to scale a given integration solution without scaling others integration solutions.

31

Future Integration needs

Scalability o Container based scaling o Scaling based on the integration solution

o E.g : Ability to scale a given integration solution without scaling others integration solutions.

Next generation WSO2 Integration Platform Addressing the future Integration needs.

33

Ballerina

A new programming language, that is designed and optimized for integration, with text and graphical syntaxes

Sequence diagram programming model Modern, network-aware, data-aware, security-

aware programming system inspired by Java, Go, Maven, ...

34

Ballerina

Graphical/textual parity with ability to switch back and forth Common integration capabilities are baked into the

language:• Deep HTTP/REST/Swagger alignment• Connectors for Web APIs and non-HTTP APIs• Support for JSON, XML, (No)SQL data and mapping

No magic – no weird syntax exceptions, everything is derived from a few key language concepts

Maximize developer productivity and abstraction clarity Support high performance implementations: low latency,

low memory and fast startup

35

Ballerina Concepts

36

Ballerina Concepts

37

Ballerina Concepts

38

Ballerina Concepts

39

Ballerina Concepts

40

State of the art Integration with Ballerina

Light-weight container native runtime — Micro-integrations.

41

State of the art Integration with Ballerina

Light-weight container native runtime — Micro-integrations.

42

State of the art Integration with Ballerina

Revolutionized Graphical and textual representationo Innovative textual and graphical programming

syntax based on Sequence diagram metaphoro The graphical and textual syntaxes would

maintain parity and would be 100% interchangeable.

o Unlike GPLs (Java, Node.js), Ballerina is designed and optimized for integration - ease of integration

43

State of the art Integration with Ballerina

Orchestrations, Choreography and Multi-party interactionso Simpler to model complex orchestrations

44

State of the art Integration with Ballerina

Orchestrations, Choreography and Multi-party interactionso Multi-party interactions, Parallel-executions

45

State of the art Integration with Ballerina

Support diverse integration requirementso Client and server connectors for HTTP 1.1/2,

WebSockets, JMS, (S)FTP(S) and moreo Client connectors for BasicAuth, OAuth,

AmazonAutho Connectors for Web APIs: Twitter, GMail, LinkedIn,

Facebook, Lambda Functionso EIPs – As language features o Graphical Data/Type mapping

46

State of the art Integration with Ballerina

Performanceo Ballerina uses latest WSO2 Netty HTTP transport

(over 5x of performance improvement compared to traditional HTTP transport implementations)

o Super-fast startup and low memory foot print. (100% container native)

o Fully non-blocking execution.

47

State of the art Integration with Ballerina

Streamlined design, development, testing and deployment life cycle

“Technology for developing, maintaining, testing, deploying, and governing interfaces between applications, machines, or databases” (source : Forrester TechRadar™: Integration Technologies 2015

48

State of the art Integration with Ballerina

Streamlined design, development, testing and deployment life cycleo Configuration over code myth?o Ballerina is a programming language- Hence it support

all the generic software development lifecycle stages. o Packaging, sharing and executingo Ballerina composer : Graphical/textual editor/debugger o Testerina and Dockerinao Docker – support

49

WSO2 Enterprise Integrator 7.0

EI 7.0 : Ballerina replaces the ESB, Data Services runtime.

EI will have two parallel versions for a long time. Migration tool will be able to handle about 80% of

ESB and Data Services to Ballerina. We will continue to evolve and support Enterprise

Integrator v6! - EI v6 will have continuing minor releases - ESB users will not be left hanging

50

Conclusion

Integration middleware is not disappearing… Rather growing to cover broad integration scenarios. Micro-integration will rule the world. Next generation WSO2 Integration Platform is

addressing those new paradigm shifts in Enterprise Integration with Ballerina.

Ballerina 1.0 GA will be available as a fully fledge production-ready programming language for building integrations

51

Questions?

kasun@wso2.com

52

References

ballerinalang.org infoq.com https://medium.com/ballerinalang https://medium.com/@kasunindrasiri/rejuvenating-

enterprise-integration-with-ballerina-70b29c2c44bf#.j4w7nuu19

THANK YOU

wso2.com