Backend interview prep

Start

Enterprise Integration Patterns (EIP) Interview Questions and Answers

Master Enterprise Integration Patterns with Spring Integration interview questions covering Pipes and Filters, Message Channel, Router, Splitter, Aggregator, Transformer, Filter, Scatter-Gather, Claim Check, Idempotent Receiver, and production best practices.

Introduction

Modern enterprise applications communicate with dozens of systems:

  • REST APIs
  • Kafka
  • RabbitMQ
  • Databases
  • Payment gateways
  • FTP servers
  • Legacy applications

If every application integrates differently, the architecture quickly becomes difficult to maintain.

To solve this problem, Gregor Hohpe and Bobby Woolf introduced Enterprise Integration Patterns (EIP).

Spring Integration implements these patterns, allowing developers to build loosely coupled, scalable, and reusable integration solutions.

Enterprise Integration Architecture

flowchart LR

Application --> Gateway

Gateway --> Channel

Channel --> Filter

Filter --> Transformer

Transformer --> Router

Router --> Splitter

Splitter --> ServiceActivator

ServiceActivator --> Aggregator

Aggregator --> ExternalSystem

Q1. What are Enterprise Integration Patterns (EIP)?

Answer

Enterprise Integration Patterns (EIP) are reusable design patterns for integrating applications using messaging.

Instead of tightly coupling systems,

applications exchange messages through standardized integration components.

Benefits

  • Loose coupling
  • Scalability
  • Reusability
  • Better maintainability
  • Easier testing

Q2. What is the Pipes and Filters Pattern?

A complex integration process is divided into multiple independent processing steps.

Each filter performs one responsibility.

Example

Validate

↓

Transform

↓

Enrich

↓

Route

↓

Process

Pipes and Filters

flowchart LR

Input --> Validation

Validation --> Transformation

Transformation --> Enrichment

Enrichment --> Processing

Processing --> Output

Each filter is independent and reusable.

Q3. What is a Message Channel?

A Message Channel transports messages between components.

Responsibilities

  • Decouple sender and receiver
  • Buffer messages
  • Support asynchronous processing

Example

@Bean

MessageChannel

orderChannel(){

    return new DirectChannel();

}

Without channels, producers must know consumers directly.

Q4. What is a Message Router?

A Router sends messages to different destinations based on rules.

Example

High-value payments

↓

Fraud Service

Normal payments

↓

Payment Service

Router

flowchart TD

IncomingMessage --> Router

Router --> PaymentService

Router --> FraudService

Router --> NotificationService

Spring provides several router implementations.

Q5. What is a Splitter?

A Splitter divides one message into multiple smaller messages.

Example

Order

↓

Item1

Item2

Item3

Example

Order

↓

Product A

Product B

Product C

Splitter

flowchart TD

Order --> Splitter

Splitter --> Item1

Splitter --> Item2

Splitter --> Item3

Useful for batch processing.

Q6. What is an Aggregator?

An Aggregator combines multiple messages into one.

Example

Items processed independently

↓

Final Order

Aggregator

flowchart TD

Item1 --> Aggregator

Item2 --> Aggregator

Item3 --> Aggregator

Aggregator --> FinalOrder

Common use cases

  • Batch jobs
  • Parallel processing
  • Report generation

Q7. What is a Transformer?

A Transformer converts one message format into another.

Example

JSON

↓

Java Object

↓

XML

.transform(

Transformers

.fromJson())

Transformer

flowchart LR

JSON --> Transformer

Transformer --> JavaObject

Transformers should never contain business logic.

Q8. What is a Message Filter?

A Filter removes unwanted messages.

Example

Invalid Orders

↓

Discard

Valid Orders

↓

Continue

Filter

flowchart TD

IncomingMessage --> Filter

Filter --> ValidMessages

Filter

-.Discard.-> InvalidMessages

Filters improve system efficiency.

Q9. What is Scatter-Gather?

Scatter-Gather executes multiple operations in parallel and combines the results.

Example

Customer Dashboard

  • Account Service
  • Loan Service
  • Card Service
  • Investment Service

All execute simultaneously.

Scatter-Gather

flowchart TD

CustomerRequest --> Scatter

Scatter --> AccountService

Scatter --> LoanService

Scatter --> CardService

Scatter --> InvestmentService

AccountService --> Gather

LoanService --> Gather

CardService --> Gather

InvestmentService --> Gather

Gather --> Dashboard

This reduces response time significantly.

Q10. What are Idempotent Receiver and Claim Check Patterns?

Idempotent Receiver

Ensures duplicate messages are processed only once.

Example

Payment Event received twice

↓

Process only once

Useful for

  • Kafka
  • RabbitMQ
  • JMS

Claim Check

Stores large payloads externally.

Flow

Large File

↓

Storage

↓

Reference ID

↓

Message

Claim Check

flowchart LR

LargePayload --> Storage

Storage --> ReferenceID

ReferenceID --> Message

Reduces message size and improves throughput.

Enterprise Integration Pattern Best Practices

Keep Components Small

Each pattern should perform a single responsibility.

Use Channels

Never tightly couple producers and consumers.

Prefer Message Transformation

Instead of modifying business services.

Handle Errors Centrally

Use dedicated error channels.

Design Idempotent Consumers

Prevent duplicate processing.

Banking Example

flowchart TD

PaymentGateway --> Gateway

Gateway --> ValidationFilter

ValidationFilter --> PaymentRouter

PaymentRouter --> DomesticPayment

PaymentRouter --> InternationalPayment

DomesticPayment --> Aggregator

InternationalPayment --> Aggregator

Aggregator --> Kafka

Kafka --> NotificationService

The payment pipeline is modular, scalable, and fault tolerant.

Common Interview Questions

  • What are Enterprise Integration Patterns?
  • What is Pipes and Filters?
  • What is a Message Channel?
  • What is a Router?
  • What is a Splitter?
  • What is an Aggregator?
  • What is a Transformer?
  • What is a Message Filter?
  • What is Scatter-Gather?
  • What are Idempotent Receiver and Claim Check?

Quick Revision

Pattern Purpose
Pipes and Filters Modular processing pipeline
Message Channel Transport messages
Router Route messages
Splitter Divide messages
Aggregator Combine messages
Transformer Convert message format
Filter Remove unwanted messages
Scatter-Gather Parallel processing
Idempotent Receiver Prevent duplicate processing
Claim Check Store large payload externally

Enterprise Integration Flow

sequenceDiagram
Application->>Gateway: Send Order
Gateway->>Channel: Message
Channel->>Filter: Validate
Filter->>Transformer: Convert Format
Transformer->>Router: Route
Router->>Splitter: Split Order
Splitter->>ServiceActivator: Process Items
ServiceActivator->>Aggregator: Combine Results
Aggregator->>ExternalSystem: Final Message
ExternalSystem-->>Application: Response

Production Example – Banking Loan Processing Platform

A banking system processes loan applications from multiple channels.

Workflow

  1. Customer submits a loan application.
  2. A Gateway receives the request.
  3. A Validation Filter removes invalid applications.
  4. A Transformer converts the REST payload into an internal domain object.
  5. A Router directs applications based on loan type.
  6. A Splitter separates uploaded documents for parallel verification.
  7. Credit verification, KYC verification, and fraud checks execute simultaneously using Scatter-Gather.
  8. An Aggregator combines all verification results.
  9. An Idempotent Receiver ensures duplicate submissions are ignored.
  10. The approved loan request is published to Kafka.
flowchart LR

CustomerPortal --> LoanGateway

LoanGateway --> ValidationFilter

ValidationFilter --> Transformer

Transformer --> LoanRouter

LoanRouter --> HomeLoan

LoanRouter --> PersonalLoan

HomeLoan --> ScatterGather

PersonalLoan --> ScatterGather

ScatterGather --> Aggregator

Aggregator --> IdempotentReceiver

IdempotentReceiver --> Kafka

This architecture enables high throughput, fault tolerance, and reusable integration flows while keeping business services independent of infrastructure concerns.

Key Takeaways

  • Enterprise Integration Patterns (EIP) provide standardized solutions for integrating distributed systems through messaging.
  • Pipes and Filters divide complex workflows into reusable processing stages.
  • Message Channels decouple producers from consumers and enable asynchronous communication.
  • Routers, Splitters, and Aggregators support intelligent message routing and parallel processing.
  • Transformers convert message formats without mixing integration logic with business logic.
  • Filters eliminate unwanted messages before they reach downstream systems.
  • Scatter-Gather improves performance by executing multiple operations concurrently.
  • Idempotent Receiver and Claim Check are essential production patterns for handling duplicate messages and large payloads efficiently.
  • Combining these patterns results in scalable, maintainable, and production-ready enterprise integration solutions.