Apache Camel was recently showcased at the Quarkus Insights show (#110). The session runs 1 hour and 10 minutes, where Peter first give an overview of Apache Camel, then Claus presents the latest update on Camel JBang, and with live demos. And the last 40 minutes is focused on Camel Quarkus where Zineb shows a live coded demo. The recording can be watched from YouTube.
Testing is probably one of those operations we use to repeat most of the time while building any application. Applications in Camel world are no difference. With the advent of Camel JBang, we have a unified place that can be used to perform our testing/fine tuning locally before moving to a higher environment. During the last years of development, we have noticed that testing or fine tuning an integration directly connected to a Cloud Native environment can result a bit cumbersome.
In this post I want to share with you how to implement a complete, end-to-end Content Based Routing solution using Apache Camel, AtlasMap and Quarkus as a developer platform, including: Drools DMN Engine, Kogito. Apache Kafka is used in this solution as a message broker. Content based routing overview Here is the Enterprise Integration Pattern (EIP) diagram of the flow, annotated with some details of the components used: The focus of this solution is routing healthcare-related messages; for this demo example, messages are routed accordingly to the following decision table rules: