Developer Joy
TPF removes the repetitive parts of delivery so teams can focus on business behavior instead of plumbing.
At a Glance
Start Fast · Design in Canvas and generate a runnable baseline.
Type Safety · Shared `common` contracts catch drift at build time.
Less Boilerplate · Adapters and client layers are generated for you.
Use This When
- You want new developers productive quickly.
- Refactors are becoming risky because contracts drift across modules.
- Teams are spending too much time on integration wiring.
Operator Reuse
When teams already have stable Java compute libraries, operators let them plug those methods directly into pipeline flow from pipeline.yaml. This shortens delivery time and avoids duplicate implementations.
Business Rejections Without Workflow Collapse
Not every failed item is a platform error. TPF lets step authors model per-item rejection as an expected business path using Item Reject Sink. Teams can reject specific records, continue processing the rest of the workload, and keep a durable audit/re-drive trail. This avoids custom side channels and keeps recovery logic explicit in step code.