Apache Camel community is happy to announce the general availability of Camel K 2.1. We have worked on the introduction of a lot of new exciting feature that will further simplify the deployment and management of Camel application on Kubernetes. Let’s see what you should expect from this release. Default Camel 4 runtime As Camel 4 is out since some time already, we’ve moved our default runtime to Camel K Runtime version 3.
For the past year, we have worked on Camel JBang, that is becoming ready to be more widespread known among Camel users. In this blog I just want to quickly refer to a number of recent video recordings of Camel JBang in action. Apache Camel 4.0 with Camel JBang MQTT demo - by Claus, How to quickly build a Camel prototype with MQTT using Docker Camel JBang - Run Camel as Script using JBang by Jasvinder, with first impressions of Camel JBang Apache Camel JBang - Reload quickly running Camel via copy/paste - by Claus, a poor man’s iPaaS with Apache Camel Karavan and Camel JBang
Apache Camel 4.1 (non LTS) has just been released. This release introduces a set of new features and noticeable improvements that we will cover in this blog post. Camel Core We continue with our performance optimizations in the core. This release brings an optimized type converter, that works around JDK issue 8180450, and can bring improved performance for many scenarios, such as the content-based router and filter. DSL The XML and YAML DSL now have better support for defining bean which can be configured with properties, and references to other beans.