Enterprise Integration Patterns¶

Hohpe, & Woolf. (2003). Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison-Wesley.

Type: Book
Intellectual base: Textbook
Year: 2003
Link: https://www.enterpriseintegrationpatterns.com/
Cited from: architecture_urban_planning, cognitive_science, communication_media_studies, computer_science, economics_finance, systems_cybernetics

Cited by¶

15 citations across 15 artifacts.

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

Primes¶

Common-Medium Intermediation
- In software it is a hub-and-spoke message broker, a shared serialization format, or a service bus, so each system speaks one protocol rather than N-minus-one.
  This sourceCatalogues hub-and-spoke message brokers, canonical data models, and message buses that replace point-to-point integration with one shared medium.
Design Patterns
- This breadth—exemplified in Hohpe and Woolf's (2003) cross-system Enterprise Integration Patterns, which captured solutions for messaging-based integration across heterogeneous systems—indicates that pattern thinking is not domain-specific but a general knowledge-transfer device: wherever a practice domain has accumulated deep empirical experience across many instances, patterns can capture and transmit that experience.
  This sourceCatalogue of 65 messaging-integration patterns across heterogeneous systems; supports the cross-system breadth claim and the microservices/integration example.
  
  Supported in partVerified against the work's full text
  
  Canonical pattern catalogue relevant to microservices, but does not document a team's internal catalog.
  
  “Messaging Patterns in Today's World: Microservices and Serverless When Bobby Woolf and I started to document the patterns 20 years ago, the key technologies for distributed applications were JMS, SOAP, MSMQ, and .NET WCF.”
  From the work's full text.
  
  Read by an automated reader; not a human review. How support was checked
Legacy Integration
- Legacy integration is not the same as controlled reentry (the process of managing the deliberate re-introduction of a previously abandoned practice or standard into a system), a distinction that parallels how Hohpe and Woolf (2003) separate forward integration patterns from reintroduction patterns in enterprise systems.
  This sourceCatalogue of integration patterns separating forward-integration mechanisms (gateways, translators, message channels) from reintroduction and reconciliation patterns in enterprise systems.
Orchestration
- Held execution state → selective assignment → interface mediation → observed return → adapted next step. The cycle repeats until a terminal condition, and every arrow passes through the same locus.
  This sourceThe Process Manager pattern places a central unit that holds the state of the sequence, receives each reply back, and determines the next processing step from the accumulated intermediate results.
Prospective Memory
- The paired triggering cue comes in the prime's two flavors: a cron job binds the action to a time-based cue (run at 02:00 daily), while an event listener binds it to an event-based cue (run when this file arrives, this message is published, this row is inserted).
  This sourceCatalogs deferred-execution and event-driven messaging patterns — scheduled jobs, event handlers, message queues with delay — and reliability monitoring for missed deliveries.
Publish Subscribe
- Consider an order-processing system where a checkout service must trigger inventory updates, shipping labels, fraud screening, and analytics.
  This sourceDefines the Publish-Subscribe Channel and topic-based routing through a broker that fans messages out to interested subscribers.
Stovepipe System
- In enterprise IT each business unit runs its own customer system, inventory system, and reporting tool, each with its own customer record and identity model, so a customer who touches three units appears as three customers and a global definitional change requires N parallel edits.
  This sourceCatalogs the integration problem created when business units each run independent applications with their own data and identity models, so a single entity appears as multiple records and any cross-cutting change requires parallel edits across systems — the canonical software-architecture treatment of data silos and the shared-substrate (integration/MDM) remedy.

Mechanisms¶

Common API
- Its central payoff is combinatorial: it turns an N-by-N mesh of bespoke integrations into N implementations of one interface, so each new participant adds linear, not quadratic, integration cost.
  This sourceExplains that a canonical data model replaces pairwise translators with one translation per application, reducing integration mappings from quadratic to linear growth.
Data Mapping Specification
- Routing through a shared canonical data model rather than point-to-point pairs keeps a growing integration from turning into an unmaintainable web of one-off specs.
  This sourceShows that a shared canonical data model replaces pairwise transformations with per-application mappings, reducing translator growth as integrations scale.
Dead-Letter Queue Processing
- Its strength is keeping a drain flowing past a few un-processable items
  This sourceDescribes diverting unprocessable messages into a separate channel so normal messaging can continue and the messages remain available for diagnosis.
Error Quarantine Queue
- The pattern is old and well-understood in messaging systems as the dead-letter queue
  This sourceDefines the dead-letter queue as a standard messaging-system destination for messages that cannot be delivered.
Integration Platform
- Adding one more system means writing links to all the others — the connections multiply combinatorially.
  This sourceExplains that direct point-to-point integration among independently built applications proliferates pairwise connections as additional systems are added.
Quarantine and Reassignment Queue
- The queue is the holding area
  This sourceDefines a dead-letter channel as the destination for messages the messaging system cannot deliver.
Request-Reply Correlation
- The classic misuse is reaching for request-reply where a fire-and-forget event would do, reintroducing the latency and coupling the async substrate was chosen to avoid.
  This sourceExplains that fire-and-forget is the looser-coupled choice when no response is semantically required, while request-response introduces conversational state, latency, and network-failure concerns.
Saga Orchestration
- Its strength is legibility and control: one place holds the workflow, so progress is queryable, recovery is directed, and complex or nested business processes are far easier to author, monitor, and change than a scatter of event subscriptions.
  This sourceDefines a Process Manager as a central unit that maintains sequence state and determines the next processing step from intermediate results.

Verification¶

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Read against the text for 1 of 15 citations: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.

Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Links previously used in the corpus¶

Before the registry existed this work was also linked 9 other ways.

Registry ID ref:6aaf8526349a · see in the full table