The Illusion of Precision in Generic Dispatch Verbs
Technical teams frequently default to labeling connector arrows with the phrase 'sends to' whenever one software component dispatches data to another. While this shorthand feels intuitive during early drafting, it strips away the architectural reality of how services actually interact under operational loads.
A synchronous HTTP request waiting for an authorization token, an asynchronous event published to an append-only event stream, and a fire-and-forget UDP telemetry packet all appear identical when annotated simply as 'sends to'. Diagram consumers cannot evaluate latency profiles, failure blast radiuses, or backpressure behavior because the transport mechanism and delivery contract remain completely unstated.
The Disambiguation Formula
Split the generic connection into transport mechanism and business intent. Instead of writing 'Service A sends to Service B', state 'Service A synchronously queries authorization state from' or 'Service A emits CustomerRegistered event to'.
Clarifying this semantic relationship transforms a static visual sketch into an actionable engineering artifact. Teammates, security auditors, and site reliability engineers immediately recognize where timeouts must be tuned, where schema validation occurs, and where retry storms might compromise downstream infrastructure.