Previous
You are at the first module.
Commerce | Reading Module
Commerce 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.
01KJ3G96Y7VB8CT1ZARBR03MFX
2/22/2026 | n/a
Fiserv uCom call failures in payment-dgs for kfc_us
• Org: kfc_us • Env: production • Service: payment-dgs > [Troubleshooting Guide](https://yumbrands.atlassian.net/wiki/spaces/YCSD/pages/1518469121/Steps+for+...
commerce Same product lane: commerceKeywords: service, team, incidentRoot 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 Same product lane: commerceKeywords: service, services, orderRoot cause (configuration) aligns with L1 focus
Study Incident →
01KJ0SA4NGQPQK2VASVG9N0DCD
2/21/2026 | n/a
Latency anomaly in Temporal Cloud causing delayed workflow processing in yc-alpha-prod-promotions.bd6e0 namespace
• Env: production • Service: Temporal • Namespace: yc-alpha-prod-promotions.bd6e0 ## Key Information: Temporal Cloud integration reports latency anomaly _on ...
commerce Same product lane: commerceKeywords: service, services, orderRoot cause (configuration) aligns with L1 focus
Study Incident →
Module Content
Not StartedKey Takeaways
observability-audit/dependencies/service-dependency-map.mdobservability-audit/architecture/service-catalog.md- Payment auth failures usually hit checkout conversion first.
- Workflow or order failures usually hit confirmations and closures.
- IDP issues impact registered users; guest checkout may still operate.
Overview
This map is derived from:
observability-audit/dependencies/service-dependency-map.mdobservability-audit/architecture/service-catalog.md
Critical Services
| Service | Team | Tier | Role in Incident Triage |
|---|---|---|---|
| workflowservice | order-delivery | 1 | central order orchestration and state transitions |
| order-dgs | order-delivery | 1 | order submission and retrieval |
| payment-dgs | payments | 1 | payment authorization and vendor routing |
| payment-workflowservice | payments | 1 | post-confirmation capture/void workflows |
| go-cart-dgs | cart | 1 | cart lifecycle and downstream fan-out |
| idpservice | customer-auth | 2 | authentication and OTP flows |
| customer-dgs | customer-auth | 2 | customer profile and session dependencies |
| store-menu-dgs | store-menu | 2 | menu and store data availability |
Key Downstream Dependencies
| Dependency | Used By | Risk Type |
|---|---|---|
| Fiserv UCOM | payment-dgs, payment-workflowservice | vendor payment outage |
| Cybersource | payment services (regional) | vendor payment outage |
| DoorDash | delivery-dgs | vendor delivery disruption |
| Braze | idpservice/switchboard OTP flows | notification and auth degradation |
| Temporal | workflowservice, payment-workflowservice | orchestration stall |
| PostgreSQL/RDS | order/customer/menu/auth services | saturation, connection failures |
| Kafka | multiple services | async backlog/cascade |
Fast Impact Heuristics
- Payment auth failures usually hit checkout conversion first.
- Workflow or order failures usually hit confirmations and closures.
- IDP issues impact registered users; guest checkout may still operate.
- Menu/cart failures block order creation before payment starts.
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.