System-to-System Integration Patterns Flashcards
7 cards from real CSI practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 System-to-System Integration Patterns flashcards as text
Which pattern splits a large message into smaller chunks, routes them independently, and reassembles the results before delivering to the recipient?
Answer: Splitter-Aggregator
The Splitter-Aggregator pattern breaks a message into parts, processes them independently, then recombines the outputs into a single response.
An integration engineer needs to route an incoming order message to different fulfillment systems based on the product category field. Which EIP pattern applies?
Answer: Content-Based Router
Content-Based Router inspects message content (such as a field value) to determine which downstream endpoint should receive it.
What problem does the 'Claim Check' enterprise integration pattern solve?
Answer: Handling large payloads by storing them externally and passing only a reference token
Claim Check stores bulky message content in external storage and passes a lightweight token through the messaging channel, reducing channel load.
In a choreography-based microservices integration, how do services coordinate their actions?
Answer: Each service reacts to events and publishes its own events without a central controller
Choreography relies on each service listening for events and emitting its own events, forming a decentralized coordination without a central orchestrator.
Which protocol is commonly used for lightweight, machine-to-machine messaging in IoT system integration due to its low bandwidth overhead?
Answer: MQTT
MQTT is a publish-subscribe protocol designed for constrained environments, offering minimal overhead ideal for IoT device-to-platform integration.
When two systems exchange data using a 'shared database' integration pattern, what is the primary drawback?
Answer: Tight coupling makes it hard to change the schema without impacting all connected systems
A shared database creates tight schema coupling — any schema change by one team can break other systems that depend on the same tables.
A Saga pattern in distributed integration is primarily used to manage what?
Answer: Long-running business transactions across multiple services without a global distributed lock
The Saga pattern coordinates multi-step distributed transactions by defining compensating actions for each step to handle failures without two-phase commit.