Integration Research Center

Talk to an Analyst

Robust integration capabilities are foundational for enterprise transformation

A continuum of reliable services are required, whether expressed in a mature API approach, in message-oriented middleware, or across storage capabilities. Over time, we will explore the topic from several viewpoints: temporal integration styles, integration types, and the evolution of integration over the past 50 years.

Temporal integration styles:

  • Synchronous
  • Asynchronous
  • Publish-subscribe
  • Batch

Integration types:

  • API
  • Event-based
  • Integration service component
  • Orchestration

Enterprise Integration

Enterprise Integration graphic


The continuum of connectivity extends to files, database, memory, sockets, point-to-point, electronic data interchange, messaging, remote procedure call, service-oriented architecture, and now APIs. Regardless of transport method or temporal requirements, each has its own strengths and drawbacks. As newer methods arrive, legacy methods are still needed to cost-effectively support business needs.

Number 1


Decide on the strategy, using any of the following building blocks:

  • API strategy (research coming soon)
  • Multichannel integration strategy
  • Front-end/back-end integration
  • Others, as needed
Number 2


Ideate, define use cases, and choose the first point of contact.

Identify the specific problem and how the solution will meet business needs and enable business and technology transformation.

Create business cases, prioritize, prove, and plan.

Number 3


Build your target-state architecture from predefined best-practice building blocks.

Use architecture building blocks to speed up the decision phase.

Leverage integration architecture.

Use integration patterns.

Number 4


Select the technology platform for middleware, as well as other (cloud) functions, DevSecOps, etc.

Define the current-state and future-state architecture.

Number 5


Deploy the standardized integration process and procedures, including development, test, and disaster recovery environments.

Modify the software development lifecycle (SDLC) when necessary for oversight.

Number 6


Make decisions about integration standards enforcement/governance (standards lifecycle management).

Create a change management plan to ensure adoption across the organization.



Prioritize and sequence investments in fundamental capabilities given the maturity of the organization and business needs. Mandate usage and govern compliance to standards.



Adopt enterprise architecture (EA) standards for integration. Enable data integration as well as application integration architecture (middleware, etc.). Define DevSecOps, integration security, etc.



Deploy the solution for initial enterprise integration. This includes all environmental support for monitoring and management as well as business continuity and disaster recovery.



Provide day-to-day operational support for all environments, project support, release/lifecycle management, and continuous integration/continuous delivery (CI/CD).

Visit our Exponential IT Research Center
Over 100 analysts waiting to take your call right now: 1-519-432-3550 x2019