Previous
You are at the first module.
POS | Reading Module
Pos 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.
01KJ37PV9KHK8BNQWQF6TQB36S
2/22/2026 | n/a
Increased rate of stores marked OFFLINE in Olympus (possible 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...
pos Same product lane: posKeywords: service, store, olympusRoot cause (configuration) aligns with L1 focus
Study Incident →
01KJ088YT6CTT1FJHS3Z76S9XH
2/21/2026 | n/a
Discrepancy between Alignment store status and POS transaction activity
pos Same product lane: posKeywords: pos, store, status
Study Incident →
01KJ2TKVX9C8W6WQM1NXMVKBP7
2/22/2026 | n/a
Mismatch between store status in Alignment data and POS transaction activity
pos Same product lane: posKeywords: pos, store, status
Study Incident →
Module Content
Not StartedKey Takeaways
observability-audit/architecture/service-catalog.mdobservability-audit/runbooks/by-scenario/store-offline.mdobservability-audit/services/poseidon-pos.yaml- Single-store issue is often local/store IT.
- Multi-store regional issues often indicate network/middleware dependency.
Overview
This map is derived from:
observability-audit/architecture/service-catalog.mdobservability-audit/runbooks/by-scenario/store-offline.mdobservability-audit/services/poseidon-pos.yaml
Critical POS Services
| Service | Team | Tier | Incident Role |
|---|---|---|---|
| poseidon-pos | pos | 2 | register and order handling in store |
| parm-next-gen | olympus | 2 | order transformation and store status routing |
| olympus-mqtt | olympus | 2 | message transport to/from POS |
| olympus-dgs | olympus | 2 | POS management services |
| couchbase | sre | infra | data synchronization dependency |
Key Dependencies
| Dependency | Used By | Risk Type |
|---|---|---|
| MQTT brokers | poseidon/olympus | connection and event loss |
| Couchbase | poseidon ecosystem | replication and storage failures |
| SyncGateway | POS replication | delayed or missing store sync |
| Brand middleware | parm and brand-specific connectors | order transmission failure |
Fast Impact Heuristics
- Single-store issue is often local/store IT.
- Multi-store regional issues often indicate network/middleware dependency.
- Cross-brand POS degradation usually requires SRE and olympus engagement.
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.