Previous
You are at the first module.
Connect | Reading Module
Connect Service Topology
Status: Not Started | Pass threshold: 100% | Points: 55
L1 20 min
Best score
0%
Attempts
0
Pass rate
0%
Passed
0
Completion happens in the checkpoint panel below.
Module Navigator
Learning Guidance
Objectives
- Map core services to team ownership.
- Identify likely downstream blast radius for each service family.
- Distinguish product logic failures from infrastructure saturation.
Evidence To Capture
- Service owner and escalation path captured.
- Critical dependency path documented.
Source Artifacts
Internal source references are available for maintainers but are not exposed in deployed environments.
Field Evidence
Real incidents related to what you're learning.
01KJ45E02K07DCN4KAZGGC2SCA
2/23/2026 | n/a
Switchboard unable to dispatch events to KFC US endpoints in production
• Org: kfc_us • Env: production • Service: switchboardserviceretry1m ## Key Information: > • Switchboard is unable to dispatch events to kfc_us > > • This er...
connect Same product lane: connectKeywords: serviceRoot cause (configuration) aligns with L1 focus
Study Incident →
01KJ0M5JDDZ0MEES932WA0C6G9
2/21/2026 | n/a
Increased rate of stores marked OFFLINE in Olympus due to connection instability
• Org: tb_uk • Env: prod-hopper • Service: olympus-daemons ## Key Information: > This monitor tracks when a store status has successfully change to OFFLINE i...
connect Same product lane: connectKeywords: serviceRoot cause (configuration) aligns with L1 focus
Study Incident →
01KJ1AFEMQXFB2T93XHD93NTTQ
2/22/2026 | n/a
Latency anomaly in Temporal Cloud affecting workflow processing for yc-hopper-prod-promotions.bd6e0 namespace
• Env: production • Service: Temporal • Namespace: yc-hopper-prod-promotions.bd6e0 ## Key Information: Temporal Cloud integration reports latency anomaly _on...
commerce Keywords: service, services, orderRoot cause (configuration) aligns with L1 focus
Study Incident →
Module Content
Not StartedKey Takeaways
kepler-datadog/investigation-guide/TEAM-ROUTING.mdobservability-audit/architecture/service-catalog.mdobservability-audit/monitors/common-monitors.md- Menu dispatch failures often degrade freshness before hard outage.
- Order event dispatch failures can block downstream fulfillment steps.
Overview
This map is derived from:
kepler-datadog/investigation-guide/TEAM-ROUTING.mdobservability-audit/architecture/service-catalog.mdobservability-audit/monitors/common-monitors.md
Critical Connect Services
| Service | Team | Tier | Incident Role |
|---|---|---|---|
| byte-connect | connect | 2 | external order injection and partner integration |
| order-injection-orchestrator | connect | 2 | order ingestion flow control |
| menu-push-orchestrator | connect | 2 | partner menu synchronization |
| switchboard | cart | 2 | event dispatch to subscribers and vendors |
| switchboard listeners/consumers | cart/connect | 2 | retry and event processing path |
Key External Dependencies
| Dependency | Risk Type | Example |
|---|---|---|
| DoorDash/UberEats | order/menu integration failure | delayed or rejected aggregator orders |
| Dragontail | kitchen integration timeout | dispatch failure without direct platform outage |
| Network/DNS | distributed dispatch failures | timeout, connection refusal, nxdomain patterns |
Fast Impact Heuristics
- Menu dispatch failures often degrade freshness before hard outage.
- Order event dispatch failures can block downstream fulfillment steps.
- Single subscriber failure may be low risk; multi-subscriber failure is high risk.
Reading Checkpoint
Current score: 0%Sections complete
0/0
Checkpoint confirmed
Not yet
Reflection
0 chars
Completion requires 80% section coverage, checkpoint confirmation, and a short reflection. On completion, you will move to the next module automatically.
Add 40 more characters.
Mark at least 80% of sections complete.