If you are building event pipelines, metrics dashboards, or log analytics, there is a good chance ClickHouse sits at the end of the line. It is fast, column-oriented, and built for append-heavy workloads. The question for Camel users is usually not whether to use ClickHouse, but how to connect to it cleanly from routes. You can already reach ClickHouse through JDBC or the generic SQL component. That works — but you miss native format streaming, server-side async inserts, and the tuning knobs that make ClickHouse fast at scale.

Continue reading ❯

HOWTOS

Two weeks ago we introduced the Camel TUI – a terminal dashboard for monitoring and managing Apache Camel integrations. Since then, development has continued at a rapid pace. This post covers the latest additions landing in Camel 4.22. Open Any Project You can now launch the TUI directly from any existing Camel project – Spring Boot, Quarkus, or Camel Main – by pointing it at the project directory: camel tui .

Continue reading ❯

TOOLING

Camel 4.22 brings two features that change how Camel integrates with AI: a unified tool abstraction (camel-ai-tool) and a built-in MCP server (camel-mcp-server). Together, they let you turn any Camel route into an AI tool that works across frameworks and protocols. This post covers both features. The Problem: Fragmented Tool Definitions Before 4.22, defining AI tools in Camel meant picking a framework and committing to it. Want to expose a route as a tool for LangChain4j?

Continue reading ❯

AICAMEL