4.2 Architecture Patterns

Introduces five whole-of-government architecture patterns - from fragmented point-to-point to fully decentralized event-driven - and explains how they coexist and interoperate within a national digita

Government architecture is not a single style or pattern applied uniformly across all systems. In practice, any national digital ecosystem will contain multiple architectural patterns running side by side - legacy registries built as monoliths, sector platforms using centralized gateways and newer services designed around event-driven microservices. The goal is not to force every system into one model but to ensure that these different patterns can interoperate reliably through shared interface contracts, consistent security boundaries and common data exchange principles.

visualization of the five whole of organization architecture patterns

There are five whole of government/organization architecture patterns:

• Wild - Fragmented Point-to-Point Integration Architecture

• Monolithic - Fully Centralized Monolithic Architecture

• Centralized Service Oriented Architecture - Oriented around a Central Gateway

• Semi-Decentralized Service Oriented Architecture - Oriented around decentralized domain gateways

• Fully Decentralized Event Driven Microservice Architecture - Oriented around domain messages and their message rooms

The patterns described above represent a spectrum from fully centralized to fully decentralized. Each carries distinct trade-offs in resilience, scalability, governance overhead, vendor dependency and operational cost.

A fragmented point-to-point landscape offers autonomy but makes cross-agency service delivery unpredictable and expensive to maintain. A monolithic architecture simplifies operations at the cost of flexibility and creates a single high-impact failure point. Centralized service-oriented models introduce a shared gateway that standardizes access but concentrates risk and procurement dependency. Semi-decentralized models distribute that gateway responsibility across domains - reducing risk radius and enabling federated governance while retaining protocol-level consistency. Fully decentralized event-driven architectures allows autonomy furthest by replacing synchronous gateway calls with asynchronous message exchange, which improves resilience and independent scaling but demands stronger schema governance and distributed tracing discipline.

Whole of government architecture is not black and white: it consists of each different architectural styles which are expected to be interoperable with one another.

A full overview of each pattern is available at Architecture Comparisons V2.

Understanding where each pattern fits - and where it breaks down - is essential for making sound investment decisions for sustainable digital government. Most governments will operate across several of these patterns simultaneously and the architecture principles defined are designed to hold regardless of which pattern a particular system follows.