Plugins, Not Glue ​
TPF gives teams clear extension rules so infrastructure concerns do not leak into business functions.
At a Glance ​
Clean Extensions · Add persistence, caching, telemetry, and logging as declared plugins.
Consistent Integration · Generated callers keep plugin behaviour aligned across REST, gRPC, and local paths.
Explicit Rules · Aspect rules say where cross-cutting work runs instead of hiding it inside business functions.
Use This When ​
- Platform features keep duplicating across teams.
- Core services are getting polluted with infrastructure logic.
- You need shared extension patterns with predictable behaviour.
In TPF, an aspect is the rule that says where a plugin should run, such as before or after a step. A plugin provides the implementation, such as persistence or cache. Your business function remains focused on the domain work.
Persistence and caching are more than generic extension examples. They are the main state-and-replay primitives in TPF: persistence keeps durable business records, and cache accelerates recomputation and replay. See the dedicated value page for that combined story.