Integration is the multi-syllabic yet succinct way to say “getting a bunch of different things to work together usefully.” Looking at the integration track for Red Hat Summit, integration is the theme, but there are as many different paths as there are things to be integrated. This spans everything from messaging to API management to IoT — basically any system that requires things to communicate.
These are the sessions jumped out at me.
Tuesday, 3:30, 151A
One emerging phrase is “agile integration” — basically the ability to integrate things in fast moving environment. This explores three capabilities that are critical for integration to be agile: distribution, containers, and APIs.
Tuesday, 4:30, 151B
“iPaaS” is the acronym for “integration platform as a service,” and is essentially shorthand for saying that different Red Hat integration projects are available as native OpenShift images — containerized integration.
There are two challenges for IoT that conflict with each other — the need for security and the need for devices and services to communicate with each other. Addressing those challenges requires several different paths of integration, each bringing its own level of security and its ability to integrate different aspects of an environment, including Fuse (integration and messaging), BRMS, and 3scale API management.
AMQ 7 introduces a new, more flexible architecture, including a new router component for automatic traffic routing and rerouting, a new high availability design which doesn’t require a centralized data store, and new messaging protocol support.