October 19, 2026 · RouteRangers
File-based integration is still the plumbing of most enterprise estates. Read locks, move vs. delete, duplicate detection across a cluster, and the failure modes that lose a partner's file quietly.
Read moreOctober 12, 2026
Rolling restarts are where in-flight exchanges go to die. How Camel's graceful shutdown, route controller, and health checks fit together so a deploy drops nothing.
Read moreSeptember 21, 2026 · RouteRangers
Most Camel performance problems are threading decisions in disguise. Where to add concurrency, what seda and threads() quietly cost you, and how to size pools to the slowest thing downstream.
Read moreSeptember 18, 2026
Endpoint credentials are configuration, not code. How Camel resolves properties, where the vault components fit, what reload-on-secret-change actually does, and the failure modes to plan for.
Read moreSeptember 16, 2026
Camel JBang runs a single route file with no build, no pom, and no scaffolding. What it is genuinely good at, where it stops, and how `camel export` turns a spike into a real Maven project.
Read moreSeptember 15, 2026
Retries alone turn a slow dependency into an outage. How to use Resilience4j circuit breakers, throttling, and real backpressure in Camel routes — and where each one belongs.
Read moreSeptember 14, 2026 · RouteRangers
Three supported ways to run Camel 4 on Kubernetes, and the operational trade-offs that actually decide it: startup and memory, build pipeline, operator dependency, and who carries the pager.
Read moreSeptember 11, 2026 · RouteRangers
Most Camel test suites either mock nothing and need a live broker, or mock everything and prove nothing. A layered approach: unit tests with AdviceWith and mock endpoints, integration tests with Testcontainers, and what belongs in neither.
Read moreSeptember 10, 2026 · RouteRangers
Traces show you where a message went; metrics tell you whether the estate is healthy. How to wire OpenTelemetry and Micrometer into Camel 4 without drowning in spans.
Read moreMay 11, 2026
Camel 2 is end of life and Camel 4 is where fixes land. The staged upgrade path we use: inventory, tests first, the 3.x hop, the Java 17 step, and slice-by-slice rollout.
Read more