envoyproxy/envoy

Convert WAVM Wasm runtime to an extension

Open

#12,574 opened on Aug 10, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/wasmhelp wanted

Repository metrics

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

Description

Currently the WAVM Wasm runtime support is a define option: --define wasm=enabled or --define wasm=wavm.

Instead we can convert the WAVM runtime support to an extension and then use a registry to resolve it. We can do the same thing for V8 and any other Wasm runtimes.

Contributor guide

Research direction
Study the current WAVM runtime integration via build defines and refactor it into an extension with a registry pattern, similar to how other extensions are handled in Envoy. Ensure that the Wasm runtime can be dynamically selected without recompilation.
Tech stack
cpp
Domain
infrastructurebackend
Issue type
Refactor
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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Bazel
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25