Patterns of Enterprise Application Architecture

Fowler, M. (2002). Patterns of Enterprise Application Architecture. Addison-Wesley.

Type

Book

Intellectual base

Textbook

Year

2002

Link

https://martinfowler.com/books/eaa.html

Cited from

architecture_urban_planning, engineering_design, tech_ethics_ai_governance

Cited by

5 citations across 5 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Collingridge Dilemma
  • Software architecture — foundational choices (schemas, API contracts, framework selection) are cheap to change before dependents exist and expensive once many systems rely on them; versioned-API and strangler-fig disciplines are curve-bending responses.

    This sourceCatalogues enterprise architecture patterns and versioning/evolutionary-design disciplines that preserve revisability as dependents accumulate (the strangler-fig pattern is Fowler's own, articulated in his later writing).

• Design Patterns

  • This sourceCanonical catalog of enterprise-tier patterns (Repository, Service Layer, Unit of Work, Active Record, Data Mapper, Domain Model); extends pattern scale upward to multi-tier applications.

• Impedance Mismatch and Coupling Efficiency
  • Software architecture: Client-server communication protocol mismatches causing latency and retry overhead; API payload structure mismatches between producer and consumer systems; schema evolution mismatches creating incompatibility or redundant translation layers, the canonical "object-relational impedance mismatch" Fowler (2003) describes as a paradigm software interface problem.

    This sourceCanonical software-architecture text: names and analyzes the "object-relational impedance mismatch" between object-oriented domain models and relational database schemas, treating it as a paradigm software interface problem requiring adapter/mapping layers.

Domain-specific

• Identity map pattern
  • An identity map keys loaded objects by persistent identifier and returns the existing instance on repeat retrieval, preventing duplicate representations and inconsistent updates during one session or transaction.
• Proxy Pattern
  • Correct reasoning therefore audits access-path completeness, delegation preservation, and the advertised transparency boundary rather than merely finding a class named `Proxy`.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 1 other way.

• https://martinfowler.com/eaaCatalog/remoteProxy.html ×1

Registry ID ref:92b36d41cd24 · see in the full table