You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While gateways are primarily used in synchronous scenarios, there are also some use cases for asynchronous scenarios, such as:
The business itself is asynchronous, and after receiving an HTTP request, it needs to be first placed into a message queue, then consumed by a specific service.
In SSE (Server-Sent Events) scenarios, the gateway acts as a consumer, waiting for message queue messages to be pushed, and then pushing them to the client.
Websocket scenarios, which are similar to the above.
How to implement?
Implement a Kafka client in the Envoy wasm context, along with readMessage and writeMessage interfaces. You can refer to the redis client and the logic of the Envoy kafka broker filter.
Extend the host ABI interface and corresponding logic in proxy-wasm-cpp-host
Extend the module abi interface and corresponding logic in wasm-go/wasm-cpp/wasm-rust
The text was updated successfully, but these errors were encountered:
Why do you need it?
While gateways are primarily used in synchronous scenarios, there are also some use cases for asynchronous scenarios, such as:
How to implement?
The text was updated successfully, but these errors were encountered: