An **integration pattern** is a reusable solution to a recurring problem in connecting disparate software systems, applications, or data sources. Integration patterns provide standardized approaches for enabling communication, data exchange, and process coordination across systems that were not necessarily designed to work together. They are foundational to [[Enterprise integration|enterprise integration]], [[Distributed computing|distributed computing]], and [[Service-oriented architecture|service-oriented architecture]], and are applied widely in the design of [[Middleware|middleware]], [[Application programming interface|APIs]], and [[Data pipeline|data pipelines]]. The systematic study of integration patterns was significantly advanced by [[Gregor Hohpe|Gregor Hohpe]] and [[Bobby Woolf]] in their 2003 work *Enterprise Integration Patterns*, which catalogued a canonical set of patterns for [[Message-oriented middleware|message-oriented]] integration. Core categories include [[Message passing|messaging]] patterns — such as [[Message queue|message queues]], [[Publish–subscribe pattern|publish-subscribe]], and [[Event-driven architecture|event-driven]] architectures — as well as [[Data transformation|transformation]] patterns, [[Routing|routing]] patterns, and [[Endpoint|endpoint]] patterns. Each pattern addresses a specific integration challenge, such as decoupling producers from consumers, handling message ordering, managing failures, or reconciling incompatible data formats. Integration patterns are implemented through a range of technologies and architectural styles. [[Enterprise service bus|Enterprise service buses]] and [[Message broker|message brokers]] such as [[Apache Kafka|Kafka]] and [[RabbitMQ]] operationalize messaging patterns at scale. [[Extract, transform, load|ETL]] and [[Extract, load, transform|ELT]] pipelines apply transformation and routing patterns in [[Data warehouse|data warehousing]] contexts. [[Microservices architecture|Microservices]] architectures rely heavily on patterns such as [[API gateway|API gateway]], [[Saga pattern|saga]], and [[Circuit breaker pattern|circuit breaker]] to manage inter-service communication and resilience. The selection of appropriate integration patterns has significant implications for system [[Coupling (computer programming)|coupling]], [[Scalability|scalability]], [[Fault tolerance|fault tolerance]], and [[Data consistency|data consistency]]. # Examples - [[Batch API-to-Warehouse ELT|Batch API-to-Warehouse ELT]] - [[MDM Hub-and-Spoke with Operational Writeback and Analytical Replication|MDM Hub-and-Spoke with Operational Writeback and Analytical Replication]] - [[Multi-Source CMDB Ingestion via Scripted API Integration with IRE Reconciliation|Multi-Source CMDB Ingestion via Scripted API Integration with IRE Reconciliation]] - [[Scheduled Flat File Ingestion via SFTP-to-Import Set Pipeline|Scheduled Flat File Ingestion via SFTP-to-Import Set Pipeline]] - [[ITSM eBonding Integration|ITSM eBonding Integration]] -