Container and Kubernetes Ready

The Pipeline Framework (TPF) generates standard Quarkus service runtimes that fit container and Kubernetes deployments, while still giving teams a practical path from one deployable to split layouts later.

See the Runtime Layouts guide for the packaging details: choosing a monolith-style runtime does not automatically remove per-step service modules because build topology and runtime layout are separate decisions.

At a Glance

Container-Friendly Runtime · Use standard Quarkus service runtimes that fit normal container and Kubernetes operations.

Fast First Release · Start with one application when that is the fastest path.

Clear Migration Path · Move to grouped or modular layouts as service splits become clearer.

No Core Rewrite · Keep the typed business functions stable while runtime layout and build topology evolve.

Use This When

• You need speed now but know service ownership and deployment splits will evolve.
• Team ownership is outgrowing a single deployable unit.
• You want normal container or Kubernetes operations without giving up a later path to split runtimes.
• Architecture discussions are stalling delivery.

TPF separates runtime layout from build topology. Runtime layout is the logical shape of the running system: where the orchestrator, functions, and side effects live. Build topology is the Maven and container structure that physically produces deployables. Changing the runtime layout changes generated placement and calls; it does not automatically rewrite Maven modules.

Jump to Guides

• Runtime Layouts
• Using Runtime Mapping
• Maven Migration Playbook
• POM vs Layout Matrix