How to quickly run 100 Camels with Apache Camel, Quarkus and GraalVM
Today I continue me practice on youtube and recorded a 10 minute video on creating a new Camel and Quarkus project that includes Rest and HTTP services with health checks and metrics out of the box.
Then comparing the memory usage of running the example in JVM mode vs native compiled with GraalVM. Then showing for the finale how to quickly run 100 instances of the example each on their own TCP port and how quick Camel are to startup and service the first requests faster than you can type and click.
A few days ago Apache Camel 3.2 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 would be either Camel 3.3 or 3.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.2.0, a new minor release with over 160 new features, improvements and fixes.
Please read our Camel 3.x upgrade guide that describes how to upgrade Camel 3.1 applications to Camel 3.2.
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.