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,600+ 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

During the last years we’ve worked hard to bring cloud native operations capabilities for your Camel workloads on Kubernetes. Camel K was the first historic initiative and it gave us the possibility to experiment several features that we’ve decided to move off into a brand new project: Camel Monitor Operator (formerly known as Camel Dashboard operator). Whilst Camel K will keep the focus and excel on the building and deploying part of a Camel application on the cloud, the goal of the new project is to focus on the monitoring part only.

Continue reading ❯

CAMEL KHOWTOSTOOLING