envoyproxy/envoy

Generalize and Standardize Wasm cross-Worker Shared Data (KV) and Shared Queues for general Envoy use.

Open

#9,611 opened on Jan 8, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/wasmdesign proposalhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (PR metrics pending)

Description

Envoy Wasm has mechanism for sharing data and queuing between threads/workers. These facilities are of general use and should be standardized and made available for general Envoy usage.

[optional Relevant Links:] https://docs.google.com/document/d/1YPbxuEIPwKsW4Ft73diHRBTUNbYIlrQHNnS9dXdn778/edit?usp=sharing https://github.com/envoyproxy/envoy-wasm/blob/master/source/extensions/common/wasm/context.cc#L53

Contributor guide

Research direction
Review the design document and understand the current Wasm shared data and queue implementations in Envoy, then propose a generalized API for cross worker shared data and queues.
Tech stack
cpp
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++EnvoyWasm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30