A few days ago Apache Camel 3.3 was released. This is a continuation of the work we are doing on Camel leading up to the first long term support release (LTS) that will be the next release v3.4. In case you have missed this, the release model in Camel 3.x is following the principe of LTS and non-LTS releases (like Java JDKs). For more details see this blog post.
The Camel community announces the immediate availability of Camel 3.3.0, a new minor release with 149 new features, improvements and fixes. Please read our Camel 3.x upgrade guide that describes how to upgrade Camel 3.2 applications to Camel 3.3. The artifacts are published and ready for you to download from the Central Maven repository. For more details please take a look at the release notes. Many thanks to all who made this release possible.
Change Data Capture (CDC) is a well-established software design pattern for a system that monitors and captures data changes, so that other software can respond to those events. Using a CDC engine like Debezium along with [Camel]() integration framework, we can easily build data pipelines to bridge traditional data stores and new cloud-native event-driven architectures. The advantages of CDC comparing to a simple poll-based or query-based process are: All changes captured: intermediary changes (updates, deletes) between two runs of the poll loop may be missed.