Integration / Apache Camel Interview Questions
What are the Enterprise Integration Patterns (EIPs) and how does Camel implement them?
Enterprise Integration Patterns (EIPs) are a catalogue of 65 named solutions to recurring messaging and integration problems, published by Gregor Hohpe and Bobby Woolf in 2003. Each pattern documents a proven approach — with a standard name, icon, and intent — for challenges such as routing, transformation, splitting, aggregating, and error handling in message-driven systems.
| EIP Pattern | Camel DSL | Purpose |
|---|---|---|
| Content-Based Router | choice()/when() | Route messages by content |
| Message Filter | filter(predicate) | Drop non-matching messages |
| Splitter | split(expression) | Break one message into many |
| Aggregator | aggregate(correlationId) | Combine many messages into one |
| Dead Letter Channel | deadLetterChannel(uri) | Safe failure routing after retries |
| Wire Tap | wireTap(uri) | Async side-copy for auditing |
| Recipient List | recipientList(expression) | Dynamic fan-out routing |
| Idempotent Consumer | idempotentConsumer(expr,repo) | Deduplicate messages |
| Content Enricher | enrich(uri) | Augment message from external source |
| Throttler | throttle(n) | Rate-limit message flow |
The Camel DSL maps directly to the EIP book language. The RouteBuilder is a composable canvas where EIPs chain together, replacing bespoke integration code with peer-reviewed building blocks that carry shared vocabulary across teams.
Who published the Enterprise Integration Patterns catalogue that Camel implements?
Which Camel DSL construct implements the Message Filter EIP?
More Related questions...
