Through, Across, Over, and Between for Paths

By the end of this lesson, you will be able to...

• Describe the interior route, span, transport medium, or endpoints between two technical components.

• Distinguish through, across, over, and between when explaining request and data paths.

• Trace a route without confusing path information with the source or destination from the previous lesson.

Idea in one sentence: through shows an interior route, across shows a span, over names a medium or layer, and between names the endpoints that frame a relationship.

Core Insight

The previous lesson gave us this movement trace:

The request moves from the browser to the gateway.
The gateway puts the job into the queue.
The worker takes the job out of the queue.

Those sentences identify sources, destinations, and container boundaries. They do not tell us what lies between the browser and the gateway. An architecture note adds this sentence:

The request moves through the edge proxy and the load balancer to the gateway.

Now the route is visible. The request enters an interior path, crosses a system span, uses a transport medium, and connects two endpoints. Four small prepositions give four different views:

through the edge proxy       -> interior route
across two regions           -> span from one side to another
over HTTPS                   -> transport medium or layer
between the proxy and API    -> two endpoints framing a relation

The question is no longer only, “Where is the request going?” It is, “What part of the path does the reader need to inspect?”

The Route We Need to See

Keep this request path in view:

browser
   |
   v
Madrid edge proxy
   |
   v
load balancer
   |
   v
report gateway
   |
   v
reporting API

The components have different roles in the sentence:

• the browser is the source from lesson 003;
• the reporting API is the destination;
• the edge proxy and load balancer are interior steps;
• the route may cross a region boundary;
• HTTPS is the transport layer used by the request;
• the proxy and API can be described as the two endpoints of a relationship.

The same request can therefore appear in several sentences without contradiction:

The browser sends the request to the report gateway.
The request travels through the edge proxy and the load balancer.
The traffic crosses the regional boundary.
The request travels over HTTPS.
The load balancer sits between the edge proxy and the report gateway.

Each sentence answers a different inspection question.

through: inside a route or intermediary

Use through when an object moves inside a route, channel, component, or sequence and emerges on the other side:

The request travels through the edge proxy.
Traffic flows through the load balancer.
The event passes through the validation service.
Logs move through the ingestion pipeline.

Plain meaning:

The object enters an intermediary and continues beyond it.

In the report path:

through the edge proxy and the load balancer names the components inside the route.

Through is useful when the interior matters. Compare it with the shorter endpoint sentence:

The request moves from the browser to the report gateway.

That sentence can be correct while hiding every intermediary. Add through when a reviewer needs to know which components saw or changed the request.

Through can describe a logical pipeline as well as a network hop:

The record passes through normalization before indexing.
The alert goes through the deduplication stage.

It does not mean that every internal operation is known. It marks the route component that the writer is choosing to expose.

across: from one side, region, or boundary to another

Use across when the important feature is a span: one side of a space, region, partition, or boundary to another:

The service replicates the record across two regions.
The request crosses the network across the private link.
The change was rolled out across all production clusters.
Metrics are aggregated across tenants.

Plain meaning:

The object spans or crosses a meaningful extent.

In technical writing, across often describes distribution rather than one physical crossing:

The configuration is consistent across the EU clusters.
The policy applies across all environments.

The reader should imagine a set or surface being covered. This differs from through, which focuses on an intermediary inside a path.

Compare:

The request travels through the load balancer.
The configuration is copied across three regions.

The first names an interior route. The second names a span of deployment locations.

over: use a medium, layer, or route surface

Use over when the important relation is the medium or communication layer carrying the movement:

The client sends the request over HTTPS.
The replicas communicate over the private network.
The agent uploads the archive over the control channel.
The service exposes the endpoint over HTTP/2.

Plain meaning:

The object travels using that communication medium or layer.

The older physical image is movement above a surface. Technical English uses the same word for a network, protocol, or channel. Over HTTPS tells the reader how the request is transported, not which gateway or region it visits.

This is a different dimension from location:

The request travels through the edge proxy over HTTPS.

Through names an intermediary. Over names the transport layer. Both can appear in one sentence because they answer different questions.

Do not use over to mean every kind of path. If the reader needs the intermediary, use through. If the reader needs the endpoints, use between or from and to.

between: frame a relation with two endpoints

Use between when the important information is the pair of components, locations, or states that define a relationship:

The load balancer sits between the edge proxy and the report gateway.
The connection between the worker and the queue is unstable.
Latency increased between the EU and US regions.
The contract defines a boundary between the client and the service.

Plain meaning:

Put the reader’s attention on the two sides of a relationship.

Between does not necessarily describe a message moving. It can describe position, communication, comparison, or responsibility:

There is a trust boundary between the API and the worker.
The error rate differs between the primary and standby regions.

Use between when the endpoints themselves matter. Use through when the interior intermediary matters. Use from and to when the direction of one movement matters.

A Worked Route Trace

Let us extend request R-104 from lesson 003. The request starts at 14:00 on Friday and moves from the browser to the report gateway. We now want to explain the route and its transport.

Step 1: keep the endpoints

R-104 moves from the browser to the report gateway.

This is the endpoint view. It does not tell us what happens inside the route.

Step 2: expose the intermediaries

R-104 travels through the Madrid edge proxy and the load balancer.

The path now has visible intermediate components. A trace reviewer can ask whether both components emitted a request log for R-104.

Step 3: expose the transport layer

R-104 travels through the Madrid edge proxy and the load balancer over HTTPS.

The route and transport are now separate claims. A proxy log can verify the first. TLS or protocol configuration can verify the second.

Step 4: expose a span when the request is distributed

Suppose the gateway sends the report job to workers in two regions:

The report job is replicated across the EU and US regions.

The job is not necessarily travelling through every machine in those regions. Across describes the extent of the distribution.

Step 5: frame a component relationship

The load balancer sits between the edge proxy and the report gateway.

This sentence does not add another request transition. It gives the reader a stable relationship that helps interpret the route.

The complete description is now:

At 14:00 on Friday, R-104 moves from the browser to the report gateway.
It travels through the Madrid edge proxy and the load balancer over HTTPS.
The report job is replicated across the EU and US regions.
The load balancer sits between the edge proxy and the report gateway.

The movement words reveal different intermediate states and relationships:

So far, the route has become inspectable without pretending that grammar is a network trace. Each phrase creates a claim, and each claim needs the corresponding system evidence.

Where the Naive Model Breaks

Using through for distribution

The configuration is copied through all production clusters.

This suggests that the configuration passes through the clusters as intermediaries in one route. If the intended meaning is that every cluster receives a copy, write:

The configuration is copied across all production clusters.

Using across for one intermediary

The request travels across the load balancer.

This could describe movement from one side of the load balancer to another, but it is unusual if the intended meaning is that the load balancer handles the request. Use:

The request travels through the load balancer.

Using over for the endpoint

The request travels over the API.

This makes the API sound like a surface or medium. If the API is the destination, write to the API. If the request is handled inside it, write through the API gateway only when that gateway is an intermediary.

Using between for a one-way event

The browser sends the request between the gateway.

Between needs two sides. Keep the directional movement:

The browser sends the request to the gateway.

Use between for the relationship:

The connection between the browser and the gateway is unstable.

Cost, Limits, and Signals

Path prepositions make architecture prose more informative, but every extra relation increases the number of claims a reader must verify. The trade-off is route visibility versus sentence weight.

Use through when an intermediary affects routing, authentication, transformation, or failure diagnosis. Use across when coverage, replication, or a cross-boundary span affects the decision. Use over when protocol or transport security matters. Use between when the two endpoints define a contract, trust boundary, or connection.

These words still do not prove that a packet, request, or copy completed the route. A sentence such as The request travelled through the load balancer can be grammatically precise even when the API later rejected the request. Check correlation IDs, hop logs, protocol handshakes, regional delivery records, and error responses.

The boundary is visible when two engineers draw different topologies from the same sentence. If one reads across the cluster as replication and another reads it as a single network crossing, add the endpoints or rewrite the sentence. Precision is not adding every possible detail; it is removing the ambiguity that changes the operational decision.

Common Confusions

Confusion: through and across both mean “from one side to another”

Why it is tempting:

Both can describe movement with a start and an end.

Better model:

Through focuses on an interior route or intermediary. Across focuses on a span, surface, region set, or boundary crossed.

Confusion: over means the request is physically above something

Why it is tempting:

The everyday image is movement over a surface.

Better model:

In technical English, over HTTPS, over the network, and over a private link identify the medium or layer carrying communication.

Confusion: between is a replacement for to

Why it is tempting:

The same two components appear in a handoff sentence.

Better model:

To identifies a destination for one movement. Between frames a two-sided relationship such as a connection, contract, or boundary.

Check Your Understanding

Check: A configuration is copied to every production cluster. Which sentence describes distribution rather than one intermediary route?

A. The configuration is copied through all production clusters.

B. The configuration is copied across all production clusters.

Think first, then reveal.

Answer: B. Across presents the clusters as a span or set receiving the configuration. Through would make them sound like sequential intermediaries.

Check: A request uses TLS and is handled by a proxy before it reaches the API. Complete the sentence:

The request travels ___ the proxy ___ HTTPS to the API.

Think first, then reveal.

Answer: Through the proxy over HTTPS. Through names the intermediary; over names the transport layer; to names the destination.

Practice: Rewrite a Network Note

A network note contains these drafts:

1. The request travels across the authentication proxy.
2. The policy is copied through all regions.
3. The connection is unstable to the worker and the queue.

Rewrite each sentence so its intended relation is visible. Then write one sentence that combines an intermediary and a transport layer.

Model answer:

1. The request travels through the authentication proxy.
2. The policy is copied across all regions.
3. The connection between the worker and the queue is unstable.

The request travels through the authentication proxy over HTTPS.

A good answer should identify:

• through for the proxy as an intermediary;
• across for distribution over a set of regions;
• between for the two endpoints of a connection;
• over HTTPS for the transport layer;
• to or from only when the sentence needs a directional endpoint.

Daily Practice Lines

• The request moves from the browser to the gateway.
• Traffic travels through the load balancer.
• The client sends the request over HTTPS.

Resources

• [ARTICLE] Cambridge Dictionary Grammar - Focus: Compare prepositions that describe routes, surfaces, relationships, and transport.
• [ARTICLE] MDN HTTP Overview - Focus: Separate the language of a request path from the protocol details that verify it.
• [ARTICLE] Microsoft Writing Style Guide - Focus: Keep architecture notes explicit enough for another engineer to inspect.

Key Takeaways

• Use through for an interior route or intermediary.
• Use across for a span, set of regions, or boundary from one side to another.
• Use over for a transport medium or communication layer.
• Use between for the two endpoints that frame a connection, contract, or boundary.
• Combine these with from, to, into, and out of, but keep each phrase tied to one claim that system evidence can verify.