Sequence and Parallel in different API group ?

[matzew]

Problem

With the goal for stable APIs, it might make sense to move Sequence and Parallel to a different API group, like flows.knative.dev ?

The messaging API group is for me more a home for foundational APIs, like Channel, InMemoryChannel, Subscription, or Broker.

In my opinion the Sequence and Parallel are more application specific aspects to build "application flows".

[lionelvillard]

I like the idea of having foundational messaging APIs and then build two abstractions on top of it, namely the event mesh (or event-driven service choreography) and flows (or event-driven service orchestration).

[n3wscott]

I feel like these are fundamental messaging components.

[devguyio]

I don't mind them staying in messaging, but I like the idea of moving them to a separate api group specially if we'll name it something similar to flows as an extra organization step IMHO.

[vaikas]

To reduce the churn, definitely feel strongly not even thinking about this for v0.10, we're going to revisit this in v0.11. I'd suggest we do some UX before renaming, given how much fun they've been in the past :)

[vaikas]

Decided in the task force to create a new API group, we'll have to decide on the name here.

[vaikas]

we'll use flows.knative.dev.