THE FUTURE OF INTEGRATION

Richard Seroter@rseroter

The typical integration project integrates business applications by sending thousands of XML messages per hour through an on-premises integration bus with five web services endpoints

CAUGHTBY SURPRISE

BE PREPARED

HOW DO WE GET

THERE?

INTEGRATION TODAYINDUSTRY TRENDS

HOW TO PREPARE

INTEGRATION TODAY

INTEGRATION SURVEY

32 participants from around the

world

428 projects represented

Q1: HOURLY MESSAGE VOLUME

dozens

hun-dreds

thou-sands

millions

Q2: NUMBER OF ENDPOINTS

1-4 endpoints 5-9 endpoints 10 or more endpoints

0

2

4

6

8

10

12

14

Q3: TECHNOLOGY USED

TECHNOLOGY USED USED 50% OR MORE

onpremises integration bus 94% 83%cloud-based integration bus 64% 6%

soap web services 100% 84%rest web services 85% 45%etl tools 81% 27%streamprocessing engines 38% 40%

Q4: POPULAR DESTINATIONS

0.00%

10.00%

20.00%

30.00%

40.00%

50.00%

60.00%

70.00%

80.00%

90.00% biz apps (commercial)biz apps (custom)

relational db

nosql dbdevices

Q5: DATA STRUCTURE

xml

json

text

INDUSTRY TRENDS

cloud computing

cloud computing 87%

cloud computing

what is it?

self-serviceautomatedprogrammablelayer of abstractionmultiple hosting optionsvalue-added services

cloud computing

integration implications

latencydata securitynew endpointstroubleshootingREST orientation

internet of things

internet of things

26billion

internet of things

what is it?

objects connected to Internetbi-directional communicationnew types of “things”new types of insight

internet of things

integration implications

lightweight communicationmassive data volumecountless endpointspre-filtered contentimmature security

mobility

mobility 149%

mobilitywhat is it?

mobile devicesmobile workforcemobile activity

mobility

integration implications

24x7 transactionsunpredictable usageinternet connectivitylightweight data transfer

wearables

200 million

wearables

wearables

what is it?

body-borne computersfactors in surroundingssimple to sophisticatedconstant interaction

wearables

integration implications

enterprise scenarioslightweight data exchangedata volumedata aggregation

big data

big data 64%

big data

what is it?

volume, variety, velocity (3 V’s)not fit for traditional toolsnew ways to managenew insight

big data

integration implications

latencybus as source or destinationaggregation technologynew data architectures

api-centric

api-centric12,000

+

api-centric

what is it?

easily consumable servicesoften external-facingdeveloper-centricdifferent than SOA

api-centric

integration implications

restful connectionsfewer technology adaptersless rigid schemasnew technologies

microservices

micro-services 0 100

micro-services

what is it?

fine-grained SOAarchitectural stylebuild app from small servicessmart endpoints, dumb pipes

micro-services

integration implications

more endpointscoarse-grainedindependent lifecycleorchestration matters?

pre-packaged integration

pre-packaged

integration128

pre-packaged

integration

what is it?

cheap, pre-built connectorscomposable integrationpublic endpointsorchestration built-in

pre-packaged

integration

integration implications

new expectationslittle customizationbundled adaptersoff-premises

shifting budgets

shifting budgets 90%

shifting budgets

what is it?

technology done outside ITfocus on time to marketvia 3rd parties or devs

shifting budgets

integration implications

no interest in upgrade projectsnew ways of integratinglooking at iPaaS solutions

oss adoption

oss adoption 56%

oss adoption

what is it?

mainstream usage of ossorganic communitiessource of innovation

oss adoption

integration implications

new data sourcesmore tools availablefaster rate of changelearn linux

container-based deployment

container-based

deployment

13 million

what is it?

os-level virtualizationprocess isolationlightweight and faststill maturing

container-based

deployment

container-based

deployment

integration implications

new way of thinkingoss-centricmicroservices friendly

devops

devops 61%

devops

what is it?

“lean” for ITcultureautomationmeasurementsharing

devopsintegration implications

scriptable integrationmore collaborationfewer silos

MOREdata

capacity

endpoints

volatility

LESSchattiness

friction

complexity

HOW TO PREPARE

OVERWHELMED?

engage

engage

twittermeetupsconferencesco-workers

educate

educate

new productsnew protocolsnew architectural ideasuse training!

engineer

engineer

decompose dependenciesedge technologiescomplimentary servicesautomation

THANK YOU!Richard Seroterhttp://seroter.wordpress.com@rseroter