Apache Camel 3.4 is the first LTS (Long Term Support) release of Camel 3. This release will be actively supported with regular patch releases containing important bug and security fixes for 1-year. For more details about LTS vs non-LTS releases see this blog post. So what’s in this release? This release is mostly about robustness and bug fixes. We have also continued the work to make Camel more modular and lighter.
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. What this means is that we will not do patch releases for Camel 3.
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.