Using the async-hooks API to integrate Envoy with our RPC library — Part I
Yingyu Cheng
702

I guess this solution is assuming there is NO shared async-resource object in the downstream components across multiple invocation flows(http-inbound → downstream components → outbound).

e.g: the downstream components include a connection pool based connector or a custom work queue.

I am curiousness how you resolve this.