### Abstract

Ask five engineers on your team what happens when a partner sends a malformed payload, or a downstream call fails halfway through a multi-step booking, and you'll get five different answers — a null check here, a manual retry there, a Slack thread instead of a design. Nobody wrote these down as patterns; they just accreted as fixes. Hohpe and Woolf named eight of them decades ago, and Camel on Quarkus turns each one into a route you can point at and say "that one, right there."

This talk works through the eight integration patterns that show up in nearly every service that talks to more than one other system — and builds each one live, as a Java route running on Quarkus. The same routes run unmodified on Spring Boot too; this talk builds and demos on Quarkus, which stays the lead runtime throughout.

**What you'll learn:**

- Route inbound traffic by shape and content instead of a stack of if-statements, using a content-based router
- Break a batch into individually processable pieces with a splitter, pull in reference data with a content enricher, and reassemble the result with an aggregator
- Stop a partner's duplicate delivery from corrupting downstream state with an idempotent consumer
- Contain a bad message with a dead letter channel and recover a flaky downstream call with retry with backoff — without either one taking the route down
- Coordinate a multi-service booking with a saga instead of reaching for two-phase commit

**Demos:** a content-based router splitting a mixed booking feed; a splitter/content-enricher/aggregator trio processing a batch end to end; an idempotent consumer absorbing duplicate delivery; a dead letter channel and retry with backoff catching a malformed booking without wedging the route; a saga compensating a partially completed booking across services.

**Key Takeaways:**
Attendees leave with eight patterns mapped directly onto working Camel-on-Quarkus code, and with the instinct to recognize, mid-incident, which one the failure in front of them is asking for. Each pattern is shown paired with the specific failure mode it exists to contain.

This is not about Camel's full component catalog or a survey of every runtime it can target. It's about the eight patterns that carry most Quarkus integration code, built once, correctly, so you stop reinventing them under pressure.

**Also in the repo (take-home appendix, shown only if time allows):** an AI appendix — Camel LangChain4j Chat classification inside a content-based router, `ai-tool` + LangChain4j agent tool-calling, MCP integration, and Wanaku exposing Camel routes as AI tools (Quarkus + Ollama qwen2.5:3b) — plus a three-tier testing setup.

### Level of Expertise

Intermediate — comfortable with Java; no Camel experience assumed.

### Target Audience

Integration developers, architects, and Java engineers building or maintaining Quarkus services that talk to more than one other system.

Requirements:

Laptop
Browser
Github account
Basic Java skills