### Abstract

By 3pm on a real on-call shift, "just add a retry" has already been tried, has already made things worse, and someone is now asking why the same booking got created twice. This workshop puts you inside that problem on purpose, for a full day. You'll stand up a shipping-domain integration pipeline — bookings arriving from two partners, in two formats, over two transports — take it from a single route to a hardened pipeline, then spend the afternoon injecting the failures that force you to reach for idempotent consumer, dead letter channel, and saga for real reasons instead of as an exercise. This isn't a lecture with slides between patterns. It's a full day of writing Camel routes on your chosen runtime, breaking them on purpose, and fixing them because the pipeline demands it.

**What we'll do:**

- Stand up a Camel route on your chosen runtime — Quarkus or Spring Boot — from scratch and grow it into a content-based router
- Split an inbound batch, enrich each element against a reference service, and aggregate the results back together
- Make the pipeline idempotent so a partner's duplicate delivery stops corrupting downstream state
- Add a dead letter channel and retry with backoff, and watch a poison message and a flaky call stop taking the route down with them
- Implement a saga that compensates a booking when a downstream service fails halfway through
- Optionally, build out a three-tier test suite and an AI-driven classification layer on top of the same routes

**Workshop Structure:**

- Setup & scenario orientation (30 min)
- Foundations: first routes + content-based router (45 min)
- Splitter, content enricher, aggregator over a booking batch (60 min)
- Resilience: idempotent consumer, dead letter channel, retry with backoff (60 min)
- Saga: compensating a partially completed booking across services (45 min)
- Optional module — Testing pyramid: MockEndpoint/AdviceWith (unit), Quarkus Dev Services + REST Assured (integration), Newman (API), Citrus end-to-end vs real infra via Testcontainers (45 min)
- Optional module — AI integration: LangChain4j classification in a content-based router, ai-tool tool-calling, MCP, Wanaku (Quarkus + Ollama qwen2.5:3b) (45 min)
- Debrief & pattern decision map (30 min)
- Breaks: morning 15 min + lunch 45 min + afternoon 15 min

**Technical Details:**
Participants work in Java with the Camel extensions on either Quarkus or Spring Boot — chosen at registration, with identical exercises in both. A `docker compose` stack provides Kafka, Postgres, an FTP endpoint, and a Grafana LGTM stack. Starter code is in the public repo `patterncatalyst/enterprise-integration-patterns-with-camel`; install requirements are Docker, a JDK, and Git; each exercise has a completed branch to fall back on.

### Level of Expertise

Intermediate — comfortable writing Java; no Camel or messaging background required.

### Target Audience

Developers and architects who build or maintain integrations, especially teams about to standardize on Camel as their integration runtime — on either Quarkus or Spring Boot.

Requirements:

Laptop
Browser
Github account
Basic Java Skills