JBoss Asylm Podcast episode 47: What do you call an Apache Camel with 3 humps Claus Ibsen and Luca Burgazzoli sits down with Emanual and Max (hosts) and talks about what is coming in Apache Camel 3 on topics like Camel K and Camel Quarkus. We also cover Camel’s place in the modern world with cloud native and serverless workloads. And at the end we have some bits about what’s coming next in Camel 3.
During the past months, several noticeable new features have been added to improve the developer experience of application based on Apache Camel. These updates are available in the 0.0.20 release of Visual Studio (VS) Code extension. Before going into the list of updates in detail, I want to note that I mentioned in the title the VS Code Extension release because VS Code extension is covering the broader set of new features.
The Apache Camel community introduces a new subproject in the ecosystem: Camel-Kafka-Connector. This project born as a PoC exploring the possibility of leveraging the Apache Camel components as Kafka source and sink connectors. The main idea behind the project is reusing the Camel Components’ flexibility in a simple way, through a configuration file mixing Kafka Connect configuration and Camel route definitions and options. What is Kafka Connect? It is an Apache Kafka’s framework that defines a standardized way to stream data in and out a kafka broker.