Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
THE FUTURE OF INTEGRATION Richard Seroter @rseroter
The typical integration project integrates business applications by sending thousands of XML messages per hour through...
CAUGHT BY SURPRISE
BE PREPARED
HOW DO WE GET THERE? INTEGRATION TODAY INDUSTRY TRENDS HOW TO PREPARE
INTEGRATION TODAY
INTEGRATION SURVEY 32 participants from around the world 428 projects represented
Q1: HOURLY MESSAGE VOLUME dozens hundreds thousands millions
Q2: NUMBER OF ENDPOINTS 14 12 10 8 6 4 2 0 1-4 endpoints 5-9 endpoints 10 or more endpoints
Q3: TECHNOLOGY USED TECHNOLOGY USED USED 50% OR MORE on premises integration bus 94% 83% cloud-based integration bus 64...
Q4: POPULAR DESTINATIONS biz apps (commercial) biz apps (custom) relational db nosql db devices 90.00% 80.00% 70...
Q5: DATA STRUCTURE xml json text
INDUSTRY TRENDS
cloud computing
cloud computing 87%
cloud computing what is it? self-service automated programmable layer of abstraction multiple hosting options valu...
cloud computing integration implications latency data security new endpoints troubleshooting REST orientation
internet of things
internet of things 26 billion
internet of things what is it? objects connected to Internet bi-directional communication new types of “things” new ...
internet of things integration implications lightweight communication massive data volume countless endpoints pre-fi...
mobility
mobility 149%
mobility what is it? mobile devices mobile workforce mobile activity
mobility integration implications 24x7 transactions unpredictable usage internet connectivity lightweight data transf...
wearables
wearables 200 million
wearables what is it? body-borne computers factors in surroundings simple to sophisticated constant interaction
wearables integration implications enterprise scenarios lightweight data exchange data volume data aggregation
big data
big data 64%
big data what is it? volume, variety, velocity (3 V’s) not fit for traditional tools new ways to manage new insight
big data integration implications latency bus as source or destination aggregation technology new data architectures
api-centric
api-centric 12,000+
api-centric what is it? easily consumable services often external-facing developer-centric different than SOA
api-centric integration implications restful connections fewer technology adapters less rigid schemas new technologie...
microservices
micro-services 0  100
micro-services what is it? fine-grained SOA architectural style build app from small services smart endpoints, dumb p...
micro-services integration implications more endpoints coarse-grained independent lifecycle orchestration matters?
pre-packaged integration
pre-packaged integration 128
pre-packaged integration what is it? cheap, pre-built connectors composable integration public endpoints orchestrati...
pre-packaged integration integration implications new expectations little customization bundled adapters off-premise...
shifting budgets
shifting budgets 90%
shifting budgets what is it? technology done outside IT focus on time to market via 3rd parties or devs
shifting budgets integration implications no interest in upgrade projects new ways of integrating looking at iPaaS so...
oss adoption
oss adoption 56%
oss adoption what is it? mainstream usage of oss organic communities source of innovation
oss adoption integration implications new data sources more tools available faster rate of change learn linux
container-based deployment
container-based deployment 13 million
what is it? os-level virtualization process isolation lightweight and fast still maturing container-based deployment
container-based deployment integration implications new way of thinking oss-centric microservices friendly
devops
devops 61%
devops what is it? “lean” for IT culture automation measurement sharing
devops integration implications scriptable integration more collaboration fewer silos
MORE data capacity endpoints volatility
LESS chattiness friction complexity
HOW TO PREPARE
OVERWHELMED?
engage
engage twitter meetups conferences co-workers
educate
educate new products new protocols new architectural ideas use training!
engineer
engineer decompose dependencies edge technologies complimentary services automation
THANK YOU! Richard Seroter http://seroter.wordpress.com @rseroter
Upcoming SlideShare
Loading in …5
×
Technology
4,013 views
Sep. 25, 2014

The Future of Application integration

How do industry trends like cloud computing, DevOps, internet-of-things, mobility, and wearables impact application integration? This presentation looks at some considerations for integration architects.

no profile picture user

  • Login to see the comments

The Future of Application integration

  1. 1. THE FUTURE OF INTEGRATION Richard Seroter @rseroter
  2. 2. 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
  3. 3. CAUGHT BY SURPRISE
  4. 4. BE PREPARED
  5. 5. HOW DO WE GET THERE? INTEGRATION TODAY INDUSTRY TRENDS HOW TO PREPARE
  6. 6. INTEGRATION TODAY
  7. 7. INTEGRATION SURVEY 32 participants from around the world 428 projects represented
  8. 8. Q1: HOURLY MESSAGE VOLUME dozens hundreds thousands millions
  9. 9. Q2: NUMBER OF ENDPOINTS 14 12 10 8 6 4 2 0 1-4 endpoints 5-9 endpoints 10 or more endpoints
  10. 10. Q3: TECHNOLOGY USED TECHNOLOGY USED USED 50% OR MORE on premises integration bus 94% 83% cloud-based integration bus 64% 6% soap web services 100% 84% rest web services 85% 45% etl tools 81% 27% stream processing engines 38% 40%
  11. 11. Q4: POPULAR DESTINATIONS biz apps (commercial) biz apps (custom) relational db nosql db devices 90.00% 80.00% 70.00% 60.00% 50.00% 40.00% 30.00% 20.00% 10.00% 0.00%
  12. 12. Q5: DATA STRUCTURE xml json text
  13. 13. INDUSTRY TRENDS
  14. 14. cloud computing
  15. 15. cloud computing 87%
  16. 16. cloud computing what is it? self-service automated programmable layer of abstraction multiple hosting options value-added services
  17. 17. cloud computing integration implications latency data security new endpoints troubleshooting REST orientation
  18. 18. internet of things
  19. 19. internet of things 26 billion
  20. 20. internet of things what is it? objects connected to Internet bi-directional communication new types of “things” new types of insight
  21. 21. internet of things integration implications lightweight communication massive data volume countless endpoints pre-filtered content immature security
  22. 22. mobility
  23. 23. mobility 149%
  24. 24. mobility what is it? mobile devices mobile workforce mobile activity
  25. 25. mobility integration implications 24x7 transactions unpredictable usage internet connectivity lightweight data transfer
  26. 26. wearables
  27. 27. wearables 200 million
  28. 28. wearables what is it? body-borne computers factors in surroundings simple to sophisticated constant interaction
  29. 29. wearables integration implications enterprise scenarios lightweight data exchange data volume data aggregation
  30. 30. big data
  31. 31. big data 64%
  32. 32. big data what is it? volume, variety, velocity (3 V’s) not fit for traditional tools new ways to manage new insight
  33. 33. big data integration implications latency bus as source or destination aggregation technology new data architectures
  34. 34. api-centric
  35. 35. api-centric 12,000+
  36. 36. api-centric what is it? easily consumable services often external-facing developer-centric different than SOA
  37. 37. api-centric integration implications restful connections fewer technology adapters less rigid schemas new technologies
  38. 38. microservices
  39. 39. micro-services 0  100
  40. 40. micro-services what is it? fine-grained SOA architectural style build app from small services smart endpoints, dumb pipes
  41. 41. micro-services integration implications more endpoints coarse-grained independent lifecycle orchestration matters?
  42. 42. pre-packaged integration
  43. 43. pre-packaged integration 128
  44. 44. pre-packaged integration what is it? cheap, pre-built connectors composable integration public endpoints orchestration built-in
  45. 45. pre-packaged integration integration implications new expectations little customization bundled adapters off-premises
  46. 46. shifting budgets
  47. 47. shifting budgets 90%
  48. 48. shifting budgets what is it? technology done outside IT focus on time to market via 3rd parties or devs
  49. 49. shifting budgets integration implications no interest in upgrade projects new ways of integrating looking at iPaaS solutions
  50. 50. oss adoption
  51. 51. oss adoption 56%
  52. 52. oss adoption what is it? mainstream usage of oss organic communities source of innovation
  53. 53. oss adoption integration implications new data sources more tools available faster rate of change learn linux
  54. 54. container-based deployment
  55. 55. container-based deployment 13 million
  56. 56. what is it? os-level virtualization process isolation lightweight and fast still maturing container-based deployment
  57. 57. container-based deployment integration implications new way of thinking oss-centric microservices friendly
  58. 58. devops
  59. 59. devops 61%
  60. 60. devops what is it? “lean” for IT culture automation measurement sharing
  61. 61. devops integration implications scriptable integration more collaboration fewer silos
  62. 62. MORE data capacity endpoints volatility
  63. 63. LESS chattiness friction complexity
  64. 64. HOW TO PREPARE
  65. 65. OVERWHELMED?
  66. 66. engage
  67. 67. engage twitter meetups conferences co-workers
  68. 68. educate
  69. 69. educate new products new protocols new architectural ideas use training!
  70. 70. engineer
  71. 71. engineer decompose dependencies edge technologies complimentary services automation
  72. 72. THANK YOU! Richard Seroter http://seroter.wordpress.com @rseroter

×