Skip to content

Core Concepts

Forage is built around a few simple ideas. Understanding them will help you get the most out of the library.

How Forage Works

In a typical Apache Camel application, you write Java code to create beans — datasources, connection factories, AI models — and register them in the Camel registry. Forage replaces that code with configuration:

graph LR
  A[Properties file] --> B[Forage discovers<br>the right provider]
  B --> C[Bean registered<br>in Camel registry]
  C --> D[Route uses it<br>by name]

You choose a name, configure it with properties, and reference it in your routes. That's it.

Key Concepts

  • Bean Providers

    How Forage discovers implementations and creates beans from your configuration.

  • Configuration

    How properties are resolved from files, environment variables, and system properties.

  • Architecture

    How the project is organized into core interfaces, implementations, and runtime adapters.

  • Runtime Support

    How the same configuration works across Camel JBang, Spring Boot, and Quarkus.