envoyproxy/envoy

M:N zone aware routing

Open

#6,333 opened on Mar 20, 2019

View on GitHub
 (5 comments) (2 reactions) (0 assignees)C++ (5,373 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Title: M:N zone aware routing

Description: Currently zone aware routing is only supported if there are equal numbers of zones for both the client and server per the documentation. It'd improve flexibility if zone aware routing can occur between M client zones and N server zones, such as if a particular service fails in one zone, the client could still try to optimize routing locally.

This seems orthogonal to https://github.com/envoyproxy/envoy/issues/1796.

Contributor guide

Research direction
Investigate how zone aware routing currently works in Envoy, particularly the equal zones limitation, and design a solution to support M:N zones. Consider the interaction with load balancing and fallback mechanisms.
Tech stack
cpp
Domain
backendnetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Distributed SystemsLoad Balancing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40