Shared queues and quiet cross-app failures
A dependency that only shows up under load can look like an unrelated outage in another team’s graph.
When apps share a queue or identity edge, a retry storm in one place can starve another without a clear error. Each team’s silo looks fine; the networked environment does not.
Before rewriting the flow, walk the journey on the paths your users actually use and watch continuity across apps. Note client-only fires versus shared-service confirmation.
Cross-App Dependency Mapping stays narrow on purpose: one coupling cluster, deep ownership notes, a checklist you can update after every cutover.