Skip to main content

Interactive Content Routing Explorer

See content routing in action! Use the interactive explorer below to step through 4 stages of content routing. Watch as messages are progressively routed to different destinations based on severity, region, event type, and priority.

How to Use This Explorer​

  1. Navigate using arrow keys (← →) or click the numbered stage buttons
  2. Compare the Input (left) and Output (right) message routing at each stage
  3. Observe how routing conditions determine destination selection (highlighted in green)
  4. Inspect the YAML code showing exactly what switch configuration was added
  5. Learn from the stage description explaining the routing technique and business benefit

Interactive Content Routing Explorer​

Original Input

All incoming messages are sent to the same destination regardless of content, severity, region, or event type. This creates compliance risks, wastes bandwidth, and provides no service level differentiation.

Use ← → arrow keys to navigate
📥Input
{
"event_id": "alert-001",
"severity": "CRITICAL",
"message": "Payment processor down",
"region": "eu-west"
}
{
"event_id": "user-002",
"severity": "INFO",
"event_type": "user.login",
"region": "us-east"
}
{
"event_id": "payment-003",
"severity": "WARN",
"event_type": "payment.failed",
"user_tier": "premium",
"region": "eu-west"
}
📤Output
→ kafka:
topic: general-events
→ kafka:
topic: general-events
→ kafka:
topic: general-events
Added/Changed
Removed
Completed Step
Current Step
Not Done Yet
📄New Pipeline Stepstep-0-original.yaml
input:
  http_server:
    address: 0.0.0.0:8080
    path: /events

output:
  kafka:
    addresses: [localhost:9092]
    topic: general-events

Try It Yourself​

Ready to build this content routing pipeline? Follow the step-by-step tutorial:

Deep Dive into Each Step​

Want to understand each routing technique in depth?

Next: Set up your environment to build this content routing pipeline yourself