Would this make WireGuard UDP tunneling over TCP easier?
Also hoping obfuscation, censorship evasion...etc!
Envoy Mobile
21–30 of 34 posts
Re: Envoy Mobile
#22So envoy will now provide a client-side library? Is there a particular reason why such client-side enhancements should not be applied to all Api clients, not just on mobile? What is the ultimate goal here? Reduce the amount of boilerplate required to handle all possible edge cases when communicating with a remote service, like need to retry, etc? I'd like to understand the value prop from a perspective of a generic a…
Consider that, on mobile, you're required to use the Android SDK or iOS SDK (or something that effectively "compiles" down to it). You can't use a sidecar app like Envoy Proxy.
On servers and desktops, applications can be built with any language and any framework. To support all of that with a library would be an expensive task that would effectively never be finished. Sure, you could pick the N most-popular languages/frameworks to support, but even that list will be moving target over time. A sidecar proxy there makes a lot more sense, and can work with any language or framework, at the expense of a bit of tighter integration.
Re: Envoy Mobile
#23I really like how they're releasing this as effectively the first working proof of concept and committing to developing the rest entirely in the open - it's a great opportunity to see how a project of this scale plays out in real-time on GitHub.
Thanks, we're excited to be able to do this in the open and welcome community involvement!
But your username is “go away please”?
Re: Envoy Mobile
#24Really interested in cases where people have taken xDS to user-scale. Presumably you would want to implement the Delta Discovery Service to minimize the bandwidth used by xDS updates, however, then you're maintaining state on the xDS server which adds server overhead.
We're adopting xDS as an abstraction for our service discovery. Implementing it has been relatively straightforward even with the relatively minimal documentation outside of the hints provided by the Envoy specific configuration elements.
Re: Envoy Mobile
#25Really interested in cases where people have taken xDS to user-scale. Presumably you would want to implement the Delta Discovery Service to minimize the bandwidth used by xDS updates, however, then you're maintaining state on the xDS server which adds server overhead. We're adopting xDS as an abstraction for our service discovery. Implementing it has been relatively straightforward even with the relatively minimal do…
Are things that complex a delta coding would be needed over sending the whole thing down if etag changes?
Re: Envoy Mobile
#26Shout out to Lyft for Envoy. I haven't used it all that much, but it's been very set and forget. The other "API gateways" like Linkerd and Kong are either a bunch of hacky Lua scripts (Kong) or use a lot of ram for the number of instances you'll probably want (Linkerd)
Re: Envoy Mobile
#27Shout out to Lyft for Envoy. I haven't used it all that much, but it's been very set and forget. The other "API gateways" like Linkerd and Kong are either a bunch of hacky Lua scripts (Kong) or use a lot of ram for the number of instances you'll probably want (Linkerd)
Linkerd uses <10mb per proxy
Re: Envoy Mobile
#28Shout out to Lyft for Envoy. I haven't used it all that much, but it's been very set and forget. The other "API gateways" like Linkerd and Kong are either a bunch of hacky Lua scripts (Kong) or use a lot of ram for the number of instances you'll probably want (Linkerd)
Kong is a fully fledged Lua/C application running on the LuaJIT VM and leveraging the NIO of Nginx, the same stack that powers the underlying proxy of companies like Cloudflare by the way.
Re: Envoy Mobile
#29Really interested in cases where people have taken xDS to user-scale. Presumably you would want to implement the Delta Discovery Service to minimize the bandwidth used by xDS updates, however, then you're maintaining state on the xDS server which adds server overhead. We're adopting xDS as an abstraction for our service discovery. Implementing it has been relatively straightforward even with the relatively minimal do…
Are things that complex a delta coding would be needed over sending the whole thing down if etag changes?
As long as the node metadata is static and you're still filtering state-of-the-world to produce the same resources. If clients are only subscribing to static resources then yes, however, if you want to perform dynamic traffic shaping across a subset of resources then you have some state to manage.
Re: Envoy Mobile
#30So does this mean that containers will be able to run on mobile devices?
No, this is a library that is linked in to a mobile app. Although arguably iOS/Android sandboxing is already akin to a container.
Ok, I'll have to dig in to find out why this is important, as all the explanations I have seen are too technical for me