Study guide

7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns

TOGAF Enterprise Architecture Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction to TOGAF & Enterprise Architecture Concepts

1.1 Overview of TOGAF Standard 10th Edition & Enterprise Architecture Concepts 1.2 The Structure of the TOGAF Standard (Easily Navigated Body of Knowledge) 1.3 Core Concepts: Enterprise, Architecture, Deliverables, Artifacts, and Building Blocks 1.4 TOGAF Certification Paths & the OGEA-101 Exam Plan

2 Chapter 2: ADM Foundation & Preliminary Phase

2.1 The Architecture Development Method (ADM) Cycle & Requirements Management 2.2 Preliminary Phase: Scope, Principles, and Architecture Capability Setup 2.3 Tailoring the ADM & Applying Iteration / Architecture Levels 2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

3 Chapter 3: ADM Architecture Vision & Business Architecture

3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition 3.2 Business Architecture Scope, Strategy & Capability Mapping 3.3 Phase B: Business Architecture Inputs, Steps, Outputs & Artifacts 3.4 Business Scenarios & Value Stream Modeling

4 Chapter 4: ADM Information Systems Architectures (Phase C)

4.1 Information Systems Architectures Overview & Phase C Strategy 4.2 Phase C Data Architecture: Principles, Data Models & Governance 4.3 Phase C Application Architecture: Logical Components, Services & Interfaces 4.4 Data and Application Integration, Migration & Interoperability

5 Chapter 5: ADM Technology Architecture & Solution Realization (Phases D, E, F)

5.1 Phase D: Technology Architecture, Platform Services & Infrastructure 5.2 Phase E: Opportunities and Solutions & Initial Implementation Strategy 5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization 5.4 Transition Architectures & Implementation Dependencies

6 Chapter 6: ADM Governance, Change & Requirements Management (Phases G, H)

6.1 Phase G: Implementation Governance & Architecture Compliance 6.2 Phase H: Architecture Change Management & Driver Monitoring 6.3 Requirements Management: Central Flow, Impact Analysis & Traceability 6.4 Architecture Contracts, Dispensations & Compliance Reviews

7 Chapter 7: BDAT Architecture Domains Deep-Dive

7.1 Business Architecture Domain: Functions, Processes & Value Streams 7.2 Data Architecture Domain: Data Entities, Storage & Data Management 7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns 7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

8 Chapter 8: Architecture Content — Content Framework, Enterprise Metamodel & Artifacts

8.1 Architecture Content Framework Overview & Deliverables vs Artifacts vs Building Blocks 8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs) 8.3 The Enterprise Metamodel: Core Concepts, Entities & Attributes 8.4 Architecture Catalogs, Matrices & Diagrams (Visual Representation) 8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

9 Chapter 9: Architecture Governance, Capability & Maturity

9.1 Architecture Governance Framework & The Role of the Architecture Board 9.2 Establishing an Architecture Capability & Organizational Structure 9.3 Architecture Skills Framework, Roles & Competency Levels 9.4 Architecture Maturity Models & Capability Assessments

10 Chapter 10: Enterprise Continuum, Reference Models & Key Techniques

10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning 10.2 Technical Reference Model (TRM) & Integrated Information Infrastructure Reference Model (III-RM) 10.3 Core EA Techniques: Gap Analysis, Interoperability, Risk, Capability-Based Planning & Architecture Patterns

7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns

Key Takeaways Explain This Topic AI

Application Services represent encapsulated functional behaviors exposed through defined interfaces, cleanly decoupling service consumers from implementation details.

Application Components are structural software packages, microservices, or custom applications that host and execute application services.

Integration patterns evolve from tightly coupled Point-to-Point connections toward Enterprise Service Bus (ESB), API Gateway, and Event-Driven Architecture (EDA) patterns.

Application Portfolio Management (APM) applies strategic evaluation frameworks like TIME (Tolerate, Invest, Migrate, Eliminate) to optimize application investments.

Interface design standards (REST, GraphQL, gRPC, SOAP) paired with Application Interaction Matrices ensure disciplined, interoperable inter-system communication.

Last updated: August 2026

7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns

Application Architecture forms the second major sub-domain of Phase C (Information Systems Architectures) in the TOGAF ADM. It provides the blueprint for the individual application systems to be deployed, their interactions, boundaries, interface contracts, and relationships to core business capabilities and data entities.

While Business Architecture defines what capabilities the enterprise requires and Data Architecture defines the underlying data structures, Application Architecture defines the software engines and service interfaces that process data and automate business capabilities.

Application Services vs. Application Components

TOGAF enforces a rigorous structural separation between Application Services and Application Components to promote loose coupling, reusability, and modularity. +---------------------------------------------------------------------------------+

  • | APPLICATION SERVICE (Behavioral Contract) |
  • | Interface: PaymentProcessingService.processPayment(amount, accountId) |
  • +---------------------------------------------------------------------------------+
  • |
  • Exposed By / Implemented By
  • v
  • +---------------------------------------------------------------------------------+
  • | APPLICATION COMPONENT (Logical / Physical Software Engine) |
  • | Component: StripePaymentGatewayAdapter / LegacyMainframeBillingModule |
  • +---------------------------------------------------------------------------------+
  • 1. Application Services (Behavioral Contracts)

An Application Service represents an encapsulated unit of business or automated behavior exposed via a well-defined interface contract. It describes what functional capability the application layer offers to external consumers (either business processes or other application components), completely hiding internal software implementation details.

Characteristics: Location-transparent, reusable, contract-driven, and access-controlled.

Example: Process Credit Card Payment , Calculate Tax Obligation , Verify Customer Identity .

2. Application Components (Implementation Engines)

An Application Component is a logical or physical software module, application executable, microservice container, or commercial off-the-shelf (COTS) package that encapsulates code and data to implement application services.

Logical Application Components: Abstract functional groupings of software logic (e.g., Customer Billing Component ).

Physical Application Components: Concrete, deployable software artifacts (e.g., billing-service-v2.1.jar , SAP S/4HANA ERP instance, Salesforce CRM cloud app).

Evolution of Enterprise Integration Patterns

As enterprise architectures scale, managing integration between applications becomes a primary architectural challenge. TOGAF architects must select appropriate Integration Design Patterns based on operational requirements, latency tolerances, and system coupling strategies.

Integration Pattern Architectural Topology Coupling Level Strengths Weaknesses & Anti-Patterns

Point-to-Point Direct Mesh Connections Tightly Coupled Simple for initial 2-3 application connections. Spaghetti integration; N ( N − 1 ) / 2 N(N-1)/2 N ( N − 1 ) /2 complexity explosion; brittle interfaces.

Enterprise Service Bus (ESB) Centralized Service Bus Medium Coupling Centralized routing, protocol transformation, message orchestration, ESB mediation. Single point of failure; bloated central bus logic; vendor lock-in heavy.

API Gateway Decentralized Edge Gateway Loosely Coupled Lightweight edge routing, OAuth2/OIDC security, rate limiting, microservices entry point. Requires decentralized governance and robust API lifecycle management.

Event-Driven Architecture (EDA) Asynchronous Event Brokers Extremely Loosely Coupled Real-time event streaming, high throughput, pub/sub scalability, fault isolation. Eventual consistency; complex event tracking, tracing, and replay management.

  • Deep-Dive into Modern Integration Architectures
  • 1. Point-to-Point Integration (Legacy Anti-Pattern)

Direct API or database-to-database connections between applications. As the system grows to N N N applications, potential connections scale exponentially according to N ( N − 1 ) 2 \frac{N(N-1)}{2} 2 N ( N − 1 ) ​ . Modifying one application interface breaks multiple dependent downstream systems.

2. Enterprise Service Bus (ESB) Pattern

A centralized architectural pattern common in Service-Oriented Architectures (SOA). The ESB acts as an intelligent communication highway providing message transformation (XML to JSON), protocol translation (SOAP to HTTP), and complex orchestration. However, ESB implementations often suffer from bloated, heavy business logic centralized inside the bus.

3. API Gateway Pattern

In modern cloud-native and microservice architectures, the API Gateway serves as the single reverse-proxy entry point for client applications. It enforces non-functional security policies (JWT validation, CORS, rate limiting, request throttling) and routes traffic to lightweight, specialized microservices.

4. Event-Driven Architecture (EDA)

EDA decouples producers from consumers using asynchronous event brokers (e.g., Apache Kafka, RabbitMQ, AWS EventBridge). Producers emit events (e.g., OrderPlacedEvent ) to an event topic without knowing which consumers will process it. Multiple independent microservices subscribe to the event topic, processing state changes asynchronously. PRODUCER EVENT BROKER CONSUMERS

  • +---------------+ +------------------+ +-------------------+
  • | Order Service | ---> [Publish] | Event Topic: | ---> [Subscribe] | Inventory Service |
  • +---------------+ | 'OrderPlaced' | +-------------------+
  • +------------------+ +-------------------+
  • --> | Shipping Service |
  • +-------------------+
  • Application Portfolio Management (APM) & The TIME Framework

During Phase C, enterprise architects conduct Application Portfolio Management (APM) to evaluate existing legacy systems and rationalize future IT investments. A standard tool recommended in enterprise governance is the TIME Framework :

Tolerate: Applications with low business value but low technical debt and low operating cost. Retain without major investment.

Invest: High business value, modern applications. Target for strategic investment, enhancement, and expansion.

Migrate: High business value but high technical debt (e.g., legacy mainframes). Retain functional capabilities while migrating underlying software to modern cloud architectures.

Eliminate: Low business value, high technical debt, and redundant applications. Target for immediate decommissioning and removal.

Standardized Interface Protocols & Deliverables

Architects define clear interface standards across application boundaries:

REST (Representational State Transfer): Resource-based HTTP/JSON APIs for web and microservices.

GraphQL: Flexible client-driven query protocol for complex client-side data fetching.

gRPC: High-performance, binary Protocol Buffer RPC framework for low-latency microservice communications.

SOAP / Web Services: Legacy XML-based messaging protocols used in enterprise legacy integration.

Essential Phase C Application Deliverables

Application Portfolio Catalog: Inventory of all logical and physical software applications.

Application / Organization Matrix: Matrix showing which organization units utilize specific applications.

Application Communication Diagram: Blueprint detailing application components, interfaces, ports, and protocols.