Apache Camel 4: what to expect
summary
Camel 4 targets Java 17 minimum and Jakarta 10 compatibility, adds tooling like Camel JBang prototype runner and the visual Camel Caravan editor, and introduces a JUnit 5 extension, internal plugin manager cleanup, SBoM output and s390x clean builds. Performance work yields concrete gains: Cedar shows up to 51% throughput gain in contention tests and Disruptor about 36% faster in multi-producer scenarios; overall many core paths are measurably faster. Migration is intended as a near drop‑in from Camel 3, but expect SLF4J 2.x dependency adjustments and 33 components flagged (about 20 easily replaceable).
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:09The Apache Camel Project
- 2:21Camel JBang
- 3:40Camel Karavan
- 4:36Motivations for Camel 4
- 6:34Build a foundation for the future
- 8:13Simplify our build and release
- 9:15Reduce our maintenance effort
- 10:33Deprecated component
- 12:45Internal changes
- 17:58Performance improvements: SEDA
- 18:40Performance improvements: disruptor
- 19:02Performance improvements: overall
- 20:40What to expect?
- 21:19Planning the upgrade
- 22:46The path to Apache Camel 4
- 23:27Migrating from Camel 3
- 25:47User-impacting changes
- 27:01Migrating from Camel 2
- 27:54Closing comments
related talks
20mApache Camel 4.0 has been released: What's new ?
44mJakarta EE 11 - Performance and Developer Productivity
01h 05mJava 11 to 17 - Exciting New Features
38mSupersonic Subatomic Apache Camel
35mGetting further with Apache Camel on Quarkus
40mMigrating from Java EE to JakartaEE 10: Challenges and Opportunities
43mWhat's New in CDI 4.0?
46mBeam Me Up, Java! A Journey through Java LTS Versions 11 to 21