Implementing Integrated Architecture in Adaptive Enterprises with the Pace‑Layered Model

Achieving Integrated Architecture in Adaptive Enterprises

In modern enterprises, a single monolithic application rarely covers the entire environment; instead, organizations operate many medium‑to‑large applications that serve various business functions, ranging from a few to hundreds depending on size and complexity.

While integration costs rise with the number of applications, moving away from a "one‑app‑does‑everything" model can reduce change costs because each small change no longer requires redeploying the entire system and re‑testing the whole stack.

Beyond cost and quantity, time is another dimension: applications evolve at different rates, making a static architectural snapshot insufficient. Recognizing these varying change velocities enables appropriate governance, testing, and DevOps practices for each layer.

Understanding the Pace‑Layered Architecture

Gartner's Pace‑Layered model divides applications into three layers:

System of Record (SOR) – Core, stable systems that support essential business functions and change slowly.

System of Differentiation – Applications that implement unique business processes, changing faster than SORs but slower than experimental solutions.

System of Innovation – Fast‑moving, sandbox‑style applications used for proofs of concept and rapid experimentation.

Integrating Within the Pace‑Layered Architecture

Integration is achieved by exposing APIs and services at each layer. Record systems expose core APIs that may be wrapped by "product adapters" to provide a more consumable interface and additional security.

In the Differentiation layer, applications combine SOR APIs with external APIs to perform data aggregation, routing, filtering, and orchestration, requiring flexible governance.

Innovation layer applications use both SOR and external APIs but operate with lighter governance to enable rapid prototyping.

A message bus (e.g., publish‑subscribe) facilitates loose coupling and scalability across and within layers.

How Microsoft Supports Pace‑Layered Integration

Microsoft offers on‑premises and cloud services to address each layer:

Record System Layer

System of Differentiation Layer

Innovation System Layer

Message Bus

For on‑premises integration, BizTalk Server provides a robust messaging engine with connectors and workflow automation. In the cloud, Azure Service Bus supports enterprise messaging, big‑data streams, event handling, and hybrid connectivity.

Tips and Best Practices

Choose integration tools based on task criticality (e.g., Logic Apps over Microsoft Flow for essential workflows).

Address security risks with API management for policy‑based governance and threat protection.

Assess solution change velocity to determine investment in automated testing and CI/CD pipelines.

Ensure the Record System layer is reliable and its APIs are well‑defined for reuse.

Enforce security and data validation close to the source.

Prefer the Differentiation layer for customizations and keep SOR customizations minimal.

Adopt a canonical data model to avoid tight coupling with vendor systems.

Use a publish‑subscribe messaging model to maximize loose coupling and scalability.

Leave room for innovation and apply appropriate governance at each layer.

Original source: https://platform.deloitte.com.au/articles/a-pace-layered-integration-architecture