Apache Camel 4.11 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 The component verifier extension has been deprecated. This functionality has not been in use for many years, and we will start to deprecate more of these unused features in camel-core going forward. Recipient List, Split and Multicast EIP In parallel processing mode, you can also enable synchronous=true to force these EIPs to process the sub-tasks using the upper bounds of the thread-pool.

Continue reading ❯

RELEASES

Introduction In the previous blog posts (camel-tensorflow-serving and camel-torchserve), we discussed the recent release of Apache Camel 4.10 LTS, which introduced three new AI model serving components. 1 TorchServe component TensorFlow Serving component KServe component We previously wrote about the TorchServe and TensorFlow Serving components. This post introduces the KServe component, concluding the series. KServe Component KServe is a platform for serving AI models on Kubernetes. KServe defines an API protocol enabling clients to perform health checks, retrieve metadata, and run inference on model servers.

Continue reading ❯

AI

Observability is a pillar of any distributed Microservices oriented architecture. As the number of services to govern may rise in number, it’s very important to have a clear and easy way to understand (observe) what’s going on in a distributed system at any time. And this feature become even more important when you’re running your application in the cloud. What is Observability from Camel perspective The term Observability is often used with a wide perspective and may provide misunderstanding about what it really encompass.

Continue reading ❯

HOWTOS