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.

Continue reading ❯

HOWTOSCAMEL KTOOLING

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:

Continue reading ❯

CAMEL QUARKUSUSECASES

In Camel K version 10, we’ve released the CLI `promote feature that provides Camel K an opinionated way of promoting an Integration through the stages of software development. This feature unlock the possibility to combine Camel K with external tooling and let the user develop according to any automated release process. We always ear about CI/CD (Continuous Integration/Continuous Delivery and/or Deployment), and in this blog we’re going to see how to make it for any Camel K integration.

Continue reading ❯

HOWTOSCAMEL K