https://github.com/tetratelabs/proxy-wasm-go-sdk

WebAssembly for Proxies (Go SDK)
https://github.com/tetratelabs/proxy-wasm-go-sdk

envoy envoyproxy extension go proxy proxy-wasm tinygo wasm webassembly

Last synced: about 1 month ago
JSON representation

WebAssembly for Proxies (Go SDK)

• Host: GitHub
• URL: https://github.com/tetratelabs/proxy-wasm-go-sdk
• Owner: tetratelabs
• License: apache-2.0
• Archived: true
• Created: 2020-03-25T09:18:13.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2024-07-27T19:59:09.000Z (5 months ago)
• Last Synced: 2024-08-01T19:42:40.020Z (4 months ago)
• Topics: envoy, envoyproxy, extension, go, proxy, proxy-wasm, tinygo, wasm, webassembly
• Language: Go
• Homepage:
• Size: 1.84 MB
• Stars: 686
• Watchers: 22
• Forks: 148
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• my-awesome - tetratelabs/proxy-wasm-go-sdk - wasm,tinygo,wasm,webassembly pushed_at:2024-07 star:0.7k fork:0.2k WebAssembly for Proxies (Go SDK) (Go)

README

        
> [!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](https://github.com/tetratelabs/proxy-wasm-go-sdk/issues/450#issuecomment-2253729297) by a long-time community member)

> as well as [the project state of Proxy-Wasm in general](https://github.com/envoyproxy/envoy/issues/35420).

> 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.