envoyproxy / envoyproxy/envoy

Support one-to-one mapping of upstream/downstream connections

Open
#12,370 17 comments 0 reactions 0 assignees View on GitHub
area/http design proposal help wanted
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
437

Description

I’d like to have the ability to have exactly one upstream connection for every downstream connection that we decide to route. That is, streams on the same downstream connection should share the same upstream connection, but no other streams should use that upstream connection.

The rationale for this is twofold:
1. I want to ensure that only the traffic for a single downstream client is carried over a given upstream connection. I do not want mixing of client traffic over an upstream connection. This would be solved by creating a new connection for every stream if it weren't for the second rationale
2. I want to avoid the overhead of the TCP handshake that would be needed in the connection-per-stream case.

I have time to work on this feature if there is a consensus that it makes sense.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.