Apache Camel has crossed 100,000 commits from 1,500+ contributors representing 450+ companies. Those numbers paint a picture of a broad, thriving open source community — and that picture is real. But there’s a more specific story inside the git history that’s worth telling: who actually maintains this project, day after day, year after year? The answer is remarkably consistent. A core engineering team has maintained Apache Camel since 2009 — and they’re still here.

Continue reading ❯

COMMUNITY

When you have a handful of Camel routes, understanding the message flow is straightforward. But as your application grows to tens or hundreds of routes connected through direct, seda, Kafka topics, and external services, it becomes harder to see the big picture. Which route feeds into which? Where does a message end up after three hops? Which external systems are involved? Apache Camel 4.21 introduces route topology diagrams to answer exactly these questions.

Continue reading ❯

FEATURES

If your security or compliance team has started asking “does it ship with an SBOM?”, you are not alone. The EU Cyber Resilience Act (CRA) will require SBOM delivery for software sold in the EU, US Executive Order 14028 and NIST guidance make SBOMs a federal procurement expectation, and enterprise evaluation checklists increasingly treat SBOM availability as a gate. Apache Camel has shipped SBOMs with every release since 4.0.3 — long before these regulations finalized.

Continue reading ❯

SECURITY