What is the Pipeline in Camel and how does it relate to a route?

A Pipeline is the default message flow mechanism inside a Camel route. When you chain multiple to() or process() calls, Camel creates a Pipeline: the output (the In-message of the next step equals the Out-message of the previous step) flows sequentially from step to step. In Camel 3.x the exchange is mutated in-place via getIn(), so the Out-message concept is largely implicit.

Conceptually, a route IS a Pipeline — every step writes to exchange.getIn(), and the next step reads from exchange.getIn(). The pipeline() DSL method makes this explicit but is rarely needed since chained processors already form a pipeline by default.

// These two routes are equivalent:

// Implicit pipeline (default):
from("direct:start")
    .process(new StepA())
    .process(new StepB())
    .to("mock:result");

// Explicit pipeline (same behaviour):
from("direct:start")
    .pipeline()
        .process(new StepA())
        .process(new StepB())
        .to("mock:result")
    .end();

The explicit pipeline() is useful when building sub-pipelines inside Multicast or Recipient List branches, where each branch needs its own independent processing chain. Outside of that context, a route already IS a pipeline and the explicit form adds no value.