Platform Priya
“Shared means everyone can change it on Friday.”
Who owns a shared pipeline without owning every team?
Elevator answer
The Orders team owns what “accept order” means. The platform team may own the shared Kafka connector and runtime. Sharing plumbing does not transfer the business.
3 coffee-machine misconceptions
Microservice Mike
“No owner is the purest autonomy.”
Platform Priya
“One owner must approve every method name.”
The real explanation
Shared pipelines expose an ordinary ownership question. The team that owns a business capability should own its flow’s meaning, domain decisions, and outcomes. Sharing infrastructure does not transfer that semantic ownership to the platform team.
A change to ApproveOrder belongs with Orders. A change to the provider operation that 30 flows use needs the connector owner, a compatibility policy, and a migration path. A change to Command recovery belongs with the runtime team. TPF can expose those seams; it cannot make “everyone” a useful owner.
The trade-off is a little process where broad impact exists. Good governance makes those dependencies explicit without converting every application change into a central ticket.
Trade-offs
TPF gains visible ownership boundaries. It gives up anonymous shared infrastructure.
When TPF is not a good fit
If no team can own common contracts or provide support for them, avoid creating a shared framework surface prematurely.