Artsiom Bukhautsou Senior Backend Engineer @Nord Security ## Agenda 1. Fan-in 2. Fan-out 3. Pipeline 4. Fan-in, Fan-out, Pipeline 5. Tee 🌱 ## Why learn these patterns?  channel fan-out read worker #1 worker #2 worker #3 ## Fan-out Pros - Concurrent complexity Use cases - Web scraping - Batch data processing ## Fan-out (example) worker #1 fetch write URLs URLs channel worker #2 fan-out worker #3 fetch ## Pipeline stage #1 ![Image](/uploads/

Kernel bypass when receiving data from the exchange (or other low-latency signals) - Dispatch / fan-out to processes on the same server ## Userspace Networking • Solarflare – industry standard low-latency readers don't affect the writer| |\# Consumers?|Many| |Message Size?|Variable length| |Dispatch?|Fan-out| |Type Support?|| ## Concurrent Queues |Bounded?|Yes - simpler & faster| |---|---| |Blocking readers don't affect the writer| |\# Consumers?|Many| |Message Size?|Variable length| |Dispatch?|Fan-out| |Type Support?|PODs| ## Principle #7: “Choose the right tool for the right task” ![Image](/upl

choose to send messages to consumers in a round-robin fashion ## Communication patterns (II) ## Fan-out Several logical consumers (possibly implemented by several parallel physical processes) can subscribe balancing time  (b) fan-out  ### Brokers vs

return p.Value, true } } return } ## 试试写个 append()? ## Example 5: Fan-in Fan-out // generic fan-in -- by changkun func Fanin(type T)(ins ...<-chan T) <-chan T { buf := } } go func() { wg.Wait() close(out) } return out } // generic fan-out -- by changkun func Fanout(type T)(r func(max int) int, in <-chan T, outs ...chan T) { l :=

Managing Deadlines, Cancellation, and Timeouts" 7. "Advanced Channel Patterns in Go: Pipeline, Fan-Out, and Fan-In" 8. "Understanding Go's Package Structure and Module System" 9. "Effective

out <- v.Interface() } }() return out } ’ alt=‘OCR图片’/> Channel Fan-out func fanOutReflect(ch <-chan interface{}, out []chan interface{}) { go func() {

iteration over channels — Building channel producers — Pipelines — Prime numbers with pipeline — Fan-out — Fan-in — Buffered channels — Channels are fair — Ticker channels ## Channels (experimental) Deferred because they do not allow arbitrary suspension, unlike produce, which is fully asynchronous. ## Fan-out Multiple coroutines may receive from the same channel, distributing work are doing. Also, pay attention to how we explicitly iterate over channel with for loop to perform fan-out in launchProcessor code. Unlike consumeEach, this for loop pattern is perfectly safe to use from

iteration over channels — Building channel producers — Pipelines — Prime numbers with pipeline — Fan-out — Fan-in — Buffered channels — Channels are fair — Ticker channels ## Channels Deferred values because they do not allow arbitrary suspension, unlike produce, which is fully asynchronous. ## Fan-out Multiple coroutines may receive from the same channel, distributing work between themselves. Let are doing. Also, pay attention to how we explicitly iterate over channel with for loop to perform fan-out in launchProcessor code. Unlike consumeEach, this for loop pattern is perfectly safe to use from

Building channel producers ..... 949 Pipelines ..... 949 Prime numbers with pipeline ..... 950 Fan-out ..... 951 Fan-in ..... 952 Buffered channels ..... 953 Channels are fair ..... 953 Ticker because they do not allow arbitrary suspension, unlike produce, which is fully asynchronous. ## Fan-out Multiple coroutines may receive from the same channel, distributing work between themselves. Let are doing. Also, pay attention to how we explicitly iterate over channel with for loop to perform fan-out in launchProcessor code. Unlike consumeEach, this for loop pattern is perfectly safe to use from

RISC-V rotaciona os bits nos operandos imediatos a partir de um posicionamento natural para reduzir o fan-out do sinal de instrução e o custo de multiplexação imediato por quase um fator de dois, o que simplifica