Skip to content
Pipebase

Concepts

Pipebase is built on a handful of core concepts. You don’t need to understand them all to ship your first flow, but you’ll meet them as you scale.

  • Flows — the unit of integration work. A YAML file Camel executes; a visual graph the designer renders.
  • Runtimes — Camel-runtime instances flows deploy to. One per environment, connected by transport routes.
  • Transport routes — the promotesTo graph that defines how flows move between environments.
  • Categories — user-editable labels for grouping flows. Currently UI-only.
  • Mesh — cross-runtime communication via Kafka
    • Pulsar. Opt-in via --profile mesh.
  • Flow testing — given/when/then tests against a real deployed flow, with connector mocking.
  • Local dev loop — one-click local runtime with auto-deploy-on-save while you build a flow.
  • Reusable sub-flows — publish a flow as a callable unit other flows can invoke, with typed inputs.