Selective subscriptions and destination fan-out solve different delivery problems
cRUD Research TeamThe cRUD Company
Selective video subscriptions decide which participant sources a client or composition receives. Destination fan-out sends an approved Program Output to one or more external endpoints. Both can reduce repeated work and support scale, but they operate on opposite sides of the media workflow.
Confusing them creates poor architecture. A participant should not subscribe to every source merely because the programme will reach several destinations. A destination should not reconstruct the session from individual tracks when a governed output already exists. The platform should manage source selection according to role, viewport and policy, then fan out the resulting programme according to destination contracts, entitlement and readiness.
TL;DR
- Selective subscriptions control which sources a participant or compositor receives.
- Destination fan-out distributes an approved Program Output to several endpoints.
- Subscriptions belong before composition; fan-out belongs after the output is created.
- Both need session authority, policy, evidence and failure handling.
- Reuse the Program Output instead of recomposing independently for every destination.
Place each decision on the correct side of composition
Before composition, the system selects approved sources for a participant or output. After composition, the system delivers the resulting programme to audience paths, recording, replay or external destinations.
Draw this boundary explicitly so product requirements do not turn into a web of track-level destination integrations.
Two different control planes
Participant role, entitlement, focus, viewport, device and current media purpose.
Approved sources, layout, audio, presentations, captions and overlays.
Endpoint contract, format, region, timing, access and retry.
Source decisions, output identity, destination outcome, usage and cost.
Selective subscriptions protect clients and outputs
An interactive participant may need the active speaker and presentation, not every camera. A mobile viewer may need fewer source tracks than a moderator console. A compositor needs only the sources approved for Program Output.
Selection reduces decode, bandwidth and processing, but it must follow product role and avoid hiding media the participant is authorised and expected to receive.
Questions for source and destination design
- Which roles may receive or publish each source?
- Can subscriptions change with layout and focus?
- How are device and viewport limits applied?
- Which sources create the authoritative Program Output?
- Which destinations receive the same output and which require a derivative?
- How are destination credentials, limits and retries governed?
- What happens when one destination fails?
- How are usage and cost attributed to source and destination work?
A practical review sequence
First, write the current product workflow and name the owner of every important fact. Second, map the media operations and provider resources that support it. Third, run one representative scenario and retain the commands, state transitions, outputs and usage evidence. Fourth, repeat the scenario with one controlled constraint or failure.
Review the result with product, engineering and operations together. Confirm what the customer experienced, what the platform concluded and what the provider reported. Record unresolved gaps rather than filling them with assumptions. This sequence turns a general capability discussion into an evidence-backed decision that can be revisited when the product changes.
Evidence to request
Separate published capability, configured behaviour and tested outcome. Ask for the contract or documentation that defines the behaviour, then verify a representative workflow in an approved environment. Record the source, date and conditions of every result.
Useful evidence connects the customer application, authorised session, provider work, participant or output and final state. Aggregated claims can guide discovery, but they should not replace the specific evidence needed to support a product promise.
- Subscription decisions by participant and policy version.
- Program Output lineage to approved sources.
- Destination attempt, acknowledgement and final state.
- Cost records separating source transport and fan-out delivery.
Do not let one destination redefine the programme
An external endpoint can impose codec, resolution or timing requirements. Create an approved derivative when necessary, but preserve the authoritative Program Output and lineage. Avoid building a separate editorial truth for each destination.
Destination failure should not end the source session unless product policy explicitly requires it.
Operate failures independently
A source-subscription failure affects a participant or composition input. A destination failure affects one output path. Alerts and recovery should identify the correct responsibility.
Use idempotent fan-out operations and reconcile endpoint state so retries do not create duplicate broadcasts.
The cRUD Morph perspective
Deliver coordinates selective subscriptions, audience paths and destination fan-out in cRUD Morph. Orchestrate supplies role and policy, Compose creates Program Output and Assure records source and destination outcomes.
Supported destinations and transitions are confirmed during technical discovery.
Summary
Selective subscriptions choose the inputs needed by a participant or output. Destination fan-out distributes the finished programme. They solve different delivery problems and belong on different sides of composition.
Keeping them separate lets one governed Program Output serve several endpoints without sending every source everywhere.
Frequently asked questions
What is a selective video subscription?
What is destination fan-out?
Are selective subscriptions the same as simulcasting?
Should every destination create its own composition?
How does cRUD Morph coordinate both?
About this article. This article explains delivery architecture. Supported subscription controls, destinations, formats and limits depend on approved providers and integration.