Enterprise Integration Patterns¶
Hohpe, G., & Woolf, B. (2003). Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison-Wesley.
Cited by¶
10 citations across 10 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.
- 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.
- 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 (marker 366) and the microservices/integration example (marker 373).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- 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.
- Consider an order-processing system where a checkout service must trigger inventory updates, shipping labels, fraud screening, and analytics.
- 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.
- 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.
Mechanisms¶
- 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.
- Its strength is keeping a drain flowing past a few un-processable items
- 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.
- The queue is the holding area
- 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 sourceIt contrasts directly with routing driven purely by messages between participants.
- 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.
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 4 other ways.
- https://martinfowler.com/books/eip.html ×1
- https://www.enterpriseintegrationpatterns.com/patterns/messaging/ProcessManager.html ×1
- https://www.enterpriseintegrationpatterns.com/patterns/messaging/PublishSubscribeChannel.html ×1
- https://www.pearson.com/en-us/subject-catalog/p/enterprise-integration-patterns-designing-building-and-deploying-messaging-solutions/P200000009266 ×1
Registry ID ref:6aaf8526349a · see in the full table