Microintegration
•
2 likes•2,343 views
This document discusses the future of enterprise integration and the concept of micro-integration. It begins by defining enterprise integration and noting the changing integration landscape with cloud, mobile, APIs and IoT. Future integration needs include growth in integration points, agility, orchestration of complex workflows, integrating diverse applications and services, improved performance and scalability. Micro-integration is proposed as integrating microservices and other applications independently with lightweight runtimes that can be developed, deployed and scaled separately. Hybrid integration platforms are needed to support different integration scenarios from on-premise to cloud.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Microintegration
Similar to Microintegration (20)
More from Kasun Indrasiri
More from Kasun Indrasiri (8)
Recently uploaded
Recently uploaded (20)
Microintegration
- 6. Future Integra1on needs • Growth and diversity of Integra3on needs • APIs and SaaS • Internet of Things (IoT) • On-premise applica1ons • B2B, Proprietary, Legacy systems
- 7. Future Integra1on needs • Agility and ease of Integra3on • Minimum integra1on skills and opera1onal overhead. • Customize exis1ng integra1ons rapidly. • Visual modeling, debugging, trouble shoo1ng • Analy1cs – Sta1s1cs, message tracing • Error handling. • Streamlined development life cycle.
- 10. Future Integra1on needs • Orchestra3on – Implemen3ng complex orchestra3on logics • Prolifera1on of services, APIs and applica1ons to integrate. • Complexity of the orchestra1on logic increases • E.g: Nexlix API: Single API call to nested, condi1onal, parallel execu1on of mul1ple backend network. • Need a simple and agile development of orchestra1on logic – Visual modeling tools.
- 12. Future Integra1on needs • Performance • No of transac1ons and latency • Ever increasing growth of traffic. • E.g: Growth of API calls in 1 year Source : h`p://blog.mailchimp.com/10m-api-calls-per-day-more/
- 13. Future Integra1on needs • Performance – New metrics • No of transac1ons and latency per container • Startup Time • Memory foot print • Distribu1on size • Average CPU consump1on, Load Average
- 14. Future Integra1on needs • Scalability • Container based scaling • Scaling based on the integra1on solu1on • E.g : Ability to scale a given integra1on solu1on without scaling others integra1on solu1ons.
- 15. Micro-Integra1on? • Mo3va3ons • Microservices architecture • How to Integrate Microservices? • Independent development and deployment • Container Architecture.
- 21. Micro-Integra1on • Build a specific integra1on scenario and run that scenario independently with a light-weight integra1on framework. • One integra1on scenario per each run1me. • Run1me is extremely lightweight and can be deployed as a container. • Develop, deploy and scale each integra1on scenarios Independently.
- 28. Hybrid Integra1on Plaorm • On-premise Integra1on • Mission cri1cal or on-premise na1ve integra1on scenarios • Complex integra1on solu1ons • iPaaS (integraton plaorm as a service) • Applica1on and data integra1on in the Cloud with pre-built/packaged integra1on solu1ons. • Mid-complexity Integra1on scenarios • Cloud/mobile center of gravity • iSaaS (Integra1on SoJware as a Services) • Social integra1on • Designed for simple integra1on scenarios (e.g.: Facebook to Twi`er etc.) • Less a`rac1on from the enterprise domain. • API Management and Self-service provisioning.
- 29. Hybrid Integra1on Plaorm • Integra1on at different levels.. This research note is restricted to High-Tech Tuesday Webinar: Middleware Technologies — Enabl TFOREXTERNALDISTRIBUTION— Source : Gartner