Fan-out
Fan-out is a pattern in which one input or operation distributes work, messages, or tasks across multiple downstream branches or processing units.
Distributed Machine Learning Patterns
A fan-out pattern starts multiple separate workflow steps from a single upstream step so they can process the same input or output.
- How it is used
- Structures machine-learning workflows that launch independent training or serving branches from shared upstream data.
- How deep it goes
- Defines the branching pattern and works through a multi-model workflow, while deferring implementation details.
- Examples
- Uses YouTube-8M entity tagging with three training branches, two selected models, separate serving, and aggregated predictions.
- What you can do after
- Apply it to organize independent branches for training or serving within a complex machine-learning workflow.
Read how Distributed Machine Learning Patterns explains fan-out →
Learn Concurrent Programming with Go
A fan-out pattern distributes messages from one source among multiple concurrent consumers so that each message is processed by one consumer.
- How it is used
- Speeds pipeline work by load-balancing channel messages across concurrent goroutines.
- How deep it goes
- Defines shared-channel worker distribution and shows Go construction, but stops short of preserving message order.
- Examples
- Uses concurrent URL downloads, downloadPages workers, a shared input channel, and a coffee-shop queue analogy.
- What you can do after
- Build it from scratch by launching channel-reading workers and combining their outputs with fan-in.
Read how Learn Concurrent Programming with Go explains fan-out →
Related concepts
- goroutineuses · A goroutine is a lightweight function execution unit managed by the Go runtime that runs concurrently with other program activity.
- Broadcastalternative to · Broadcast is a book-specific Go function that creates multiple output channels and copies each received message to all of them.
- channeluses · A channel is a typed Go communication and synchronization mechanism through which goroutines send and receive values.
- dependencykind of · A software dependency is a component, resource, or prerequisite on which another software component or operation relies to function or proceed.
- Apache Kafkaproduced by · Apache Kafka is a distributed event-streaming platform for publishing, storing, processing, and consuming streams of records.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.