Apache Camel has shipped 272 production releases over 19 years without a single month of inactivity. The project averages a new release every 15 days, maintains up to 10 release lines in parallel, and has accumulated 100,000+ commits from over 1,500 contributors since 2007. This track record is not a recent development — it has been sustained continuously since well before the current wave of AI-driven open-source activity. This post presents the evidence.

Continue reading ❯

FEATURES

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