Integration
36 items tagged with "integration"
Best Practices2
Stripe API Versioning Policy
Backwards-compatible evolution strategy and pinned versions for API consumers.
Model Context Protocol (MCP)
The Model Context Protocol is an open standard that lets AI applications connect to external tools and data sources through a uniform client-server interface.
Patterns26
Adapter
Converts the interface of a class into another interface clients expect, letting classes that could not otherwise collaborate work together.
Adapter Microservice
A microservice that translates between an application and an external system with an incompatible interface or protocol.
Aggregator
A component that invokes multiple services and combines their responses into a single consolidated result for the caller.
Scatter-Gather
Broadcasts a request to multiple recipients in parallel, then aggregates their replies into a single response.
Pipes and Filters
Decompose complex processing into a sequence of independent components connected by channels so each step can scale and evolve.
Message Channel
Connects two applications with a logical pipe so a sender can transmit data to a receiver without knowing the receiver's location or identity.
Point-to-Point Channel
Ensures exactly one receiver consumes each message on a channel, even when multiple consumers compete, so a message is processed once.
Publish-Subscribe Channel
Broadcasts each message to all interested subscribers so one event can notify many independent consumers without the publisher knowing them.
Message Router
Consumes a message and redirects it to a different channel based on conditions, decoupling producers from the decision of where messages should go.
Content-Based Router
Routes each message to a destination channel chosen by inspecting the message's content, so the payload itself determines where it is delivered.
Message Filter
Lets only messages meeting specified criteria pass through a channel and silently discards the rest, so consumers receive only relevant messages.
Splitter
Breaks a composite message into a series of individual messages so each element can be processed independently downstream.
Message Translator
Converts a message from one data format or schema to another so systems with incompatible representations can communicate.
Content Enricher
Augments a message with additional data from an external source when the original lacks information the receiver requires.
Normalizer
Translates messages arriving in many different formats into a single common format so downstream components handle one canonical representation.
Polling Consumer
A consumer that explicitly checks a channel for messages on its own schedule, controlling exactly when and how fast it receives them.
Event-Driven Consumer
A consumer that is invoked by the messaging system the moment a message arrives, reacting to messages instead of polling for them.
Idempotent Receiver
Makes a consumer safely handle duplicate messages so that processing the same message more than once has the same effect as processing it once.
Dead Letter Channel
Routes messages that cannot be delivered or processed to a dedicated channel for inspection and recovery instead of discarding or blocking them.
Guaranteed Delivery
Persists messages so they are not lost if the sender, broker, or receiver fails, ensuring each message is eventually delivered despite outages.
Request-Reply
Lets a requestor send a message and receive a corresponding response over messaging, combining two one-way channels into a logical two-way exchange.
Correlation Identifier
Tags messages with a unique id that links related messages together, so a reply can be matched to its request and parts to their whole.
Wire Tap
Copies messages flowing through a channel to a secondary channel for inspection, logging, or analysis without disturbing the primary flow.
Routing Slip
Attaches a sequence of processing steps to a message so it routes itself through a series of components determined per message at runtime.
Process Manager
A central component that maintains the state of a multi-step message flow and decides the next step, coordinating complex or branching workflows.
Webhook
A server pushes event notifications to a client-registered HTTP endpoint as events occur, replacing inefficient polling with real-time callbacks.
Anti-Patterns2
Blueprints2
Point-to-Point Integrations to Message Bus Blueprint
Replace tangled point-to-point integrations with a central message bus and publish/subscribe model to reduce coupling and integration sprawl.
Enterprise Service Bus to Modern Integration Blueprint
Replace a heavyweight enterprise service bus with lightweight integration: API gateway, event streaming, and decentralized integration services.