Production Support & Upgrades
Keep the routes healthy, current, and fast.
Integration layers age quietly: the Camel version falls behind, the Java baseline drifts, throughput degrades a percent a month, and the one engineer who understood the routes moves on. We keep estates healthy — including estates we did not build.
Upgrades
Camel 2 is end of life and Camel 3 is maintenance-only; the 4.x line is where fixes land. We run the staged 2-to-3-to-4 path: component and DSL inventory, test coverage against current behavior first, the 3.x hop with its module split and renames, then the 4.x step with Java 17, Jakarta namespaces, and Spring Boot 3 — rolled out in slices, not as one estate-wide flag day. Our upgrade field guide describes the approach in detail.
Performance tuning
Thread pool and concurrency profiles, endpoint tuning, batching and streaming choices, aggregation memory behavior, and the measurement to prove improvements are real — against your production traffic shapes, not synthetic benchmarks.
Incident escalation
When an integration incident exceeds your team's Camel depth, we join as escalation support: diagnosis, stabilization, and a written post-incident analysis with the route-level fixes that prevent recurrence. Support arrangements are agreed per client — hourly, like everything we do — so the terms are set before the bad day, not during it.
Running an estate that has drifted behind? Get in touch — an architecture review is often the right first step.