Parallel CRD provides a way to easily define a list of branches, each receiving the same CloudEvent sent to the Parallel ingress channel. Typically, each branch consists of a filter function guarding the execution of the branch.
Subscriptions under the hood.
Parallel has three parts for the Spec:
branchesdefines the list of
subscriberpairs, one per branch, and optionally a
replyobject. For each branch:
- (optional) the
filteris evaluated and when it returns an event the
subscriberis executed. Both
- the event returned by the
subscriberis sent to the branch
replyobject. When the
replyis empty, the event is sent to the
spec.replyobject (see below).
channelTemplatedefines the Template which will be used to create
replydefines where the result of each branch is sent to when the branch does not have its own
Parallel has three parts for the Status:
conditionswhich details the overall status of the Parallel object
branchesStatuseswhich convey the status of underlying
Subscriptionresource that are created as part of this Parallel.
addresswhich is exposed so that Parallel can be used where Addressable can be used. Sending to this address will target the
Channelwhich is fronting this Parallel (same as
Learn how to use Parallel by following the examples