Every Apache Camel release ships new features and bug fixes — and those get the headlines. But behind every release there is a quieter effort that rarely gets mentioned: keeping 500+ third-party dependencies current. We compared the parent/pom.xml across every Camel 4.x minor release — from 4.0.0 to 4.20.0 — and counted every dependency version that changed. Here is what we found. 2,449 dependency updates across 20 releases Every minor release updates a significant portion of the dependency tree.
Continue reading ❯
COMMUNITY
Apache Camel has fixed 7,070 out of 7,081 reported bugs — a 99.8% resolution rate — with a median fix time of 1 day. That track record spans 19 years, 350+ connectors, and 272 production releases. This is not a recent improvement — the project has maintained a 1-day median resolution for 17 of the last 19 years. Here is the data. We pulled the numbers from JIRA, GitHub, and Maven Central to see what 19 years of Apache Camel bug data actually looks like.
Continue reading ❯
COMMUNITY
On March 19, 2007, at 10:54 UTC, James Strachan pushed commit 77b260b6 with the message “Initial checkin of Camel routing library.” It contained 42 files across two modules: camel-core and camel-jms. Nineteen years later, the repository has crossed 100,000+ commits from 1,600+ contributors, ships 350+ integration components, and runs in production from CERN’s Large Hadron Collider to UPS processing tens of billions of messages per day. Through all of that — through the rise and fall of ESBs, the SOA-to-microservices migration, the cloud-native revolution, Kubernetes, serverless, and now AI coding agents — the core DNA has remained remarkably stable.
Continue reading ❯
COMMUNITY
Rewriting critical banking ETL applications is risky because these systems handle business data that must stay accurate, stable, and traceable. In his JEurope 2025 talk, Dzmitry Paddubnik explains how his team rebuilt more than 20 banking ETL applications in Java without losing control of production risk. The main lesson is simple: a rewrite is not just a coding project. It is a testing and validation project. Key takeaways Legacy ETL systems often contain years of hidden business rules.
Continue reading ❯
COMMUNITYUSECASES
When the first commit landed on March 19, 2007, Apache Camel was a routing library with a handful of components and a single contributor. Nineteen years later, the git repository has crossed 100,000 commits from 1,500+ contributors representing 450+ companies across more than 20 countries. The project ships 311 integration components, has published 300+ releases, and runs in production at organizations where downtime means grounded flights, blocked payments, or missed diagnoses.
Continue reading ❯
COMMUNITY