Interactive Fan-Out Pattern Explorer
See multi-destination routing in action! Use the interactive explorer below to step through 5 stages of fan-out pattern implementation. Watch as data progressively gains routing capabilities to Kafka, S3, and Elasticsearch.
How to Use This Explorer
- Navigate using arrow keys (← →) or click the numbered stage buttons
- Compare the Input (left) and Output (right) YAML configuration at each stage
- Observe how destinations are added (green highlight) and configurations evolve
- Inspect the YAML code showing exactly what broker pattern was configured
- Learn from the stage description explaining the technique and edge computing benefit
Interactive Fan-Out Pattern Explorer
Single Destination
Basic pipeline with single file output - the typical starting point before implementing fan-out pattern.
Use ← → arrow keys to navigate
📥Input
{
"event_id": "sensor-001",
"sensor_id": "temp-sensor-42",
"timestamp": "2025-01-20T10:30:00Z",
"temperature": 23.5,
"humidity": 65.2
}
📤Output
→ file:
path: /var/data/events.jsonl
// Single destination - no redundancy
Added/Changed
Removed
Completed Step
Current Step
Not Done Yet
📄New Pipeline Stepsingle-destination.yaml
name: single-destination-pipeline
type: pipeline
config:
input:
http_server:
address: 0.0.0.0:8080
path: /events
output:
file:
path: /var/data/events.jsonl
codec: linesTry It Yourself
Ready to build this multi-destination pipeline? Follow the step-by-step tutorial:
Deep Dive into Each Step
Want to understand each routing technique in depth?
- Step 1: Configure Broker - Set up fan-out foundation
- Step 2: Add Kafka - Real-time streaming integration
- Step 3: Add S3 - Long-term archive integration
- Step 4: Add Elasticsearch - Search and analytics integration
- Step 5: Implement Fallbacks - Edge resilience patterns
Next: Set up your environment to build this multi-destination pipeline yourself