-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ProxyWasm plugin rewrite in Rust #426
Comments
Still active fork: https://github.com/higress-group/proxy-wasm-go-sdk |
I think that because of the argument about why it is no longer recommended I'd prefer to rewrite it in Rust. |
there's a new "official" fork https://github.com/proxy-wasm/proxy-wasm-go-sdk |
That's interesting, I will try porting the actual plugin to the new fork as they seem to need active users for this. |
Yeah! We're excited about it. Note the key difference: this is full go, not tiny go. That solves a ton of problems with memory management and capabilities. It depends on not-yet-mainstream Go 1.24. Please let us know how it works for you! CC @leonm1 |
ProxyWasm go SDK was archived: https://github.com/tetratelabs/proxy-wasm-go-sdk
Warning
We are no longer recommending this SDK or Wasm in general for anyone due to the fundamental memory issue of TinyGo (See the detailed explanation by a long-time community member)
as well as the project state of Proxy-Wasm in general.
If you are not in a position where you have to run untrusted binaries (like for example, you run Envoy proxies while your client gives you the binaries to run), we recommend using other extension mechanism
such as Lua or External Processing which should be comparable or better or worse depending on the use case.
If you are already using this SDK, but still want to continue using Wasm for some reason instead of Lua or External Processing,
we strongly recommend migrating to the Rust or C++ SDK due to the memory issue of TinyGo described in the link above.
We keep this repository open and not archived for the existing users, but we cannot provide any support or guarantee for the future development of this SDK.
However, at any time, we may decide to archive this repository if we see no reason to keep it open.
The text was updated successfully, but these errors were encountered: