zng00

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.

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

Wow, these are some great resources. Thanks for sharing! I have a call with one of your colleagues in 5 minutes ;)

This is great, thanks for sharing. I'm curious about the downstream proxy process (i.e. ::1234) and how you scale it and balance load across multiple instances of the process. You can't really use iptables to load balance your processes as either the DNAT or REDIRECT mechanism will modify the destination address, right?

Ex. # TPROXY directs all traffic to :1234, and these rules load balance to 4 different processes

iptables -t nat -I OUTPUT -p tcp -o lo --dport 1234 -m state --state NEW -m statistic --mode nth --every 4 --packet 0 -j DNAT --to-destination 127.0.0.1:8080

iptables -t nat -I OUTPUT -p tcp -o lo --dport 1234 -m state --state NEW -m statistic --mode nth --every 4 --packet 1 -j DNAT --to-destination 127.0.0.1:8081

iptables -t nat -I OUTPUT -p tcp -o lo --dport 1234 -m state --state NEW -m statistic --mode nth --every 4 --packet 2 -j DNAT --to-destination 127.0.0.1:8082

iptables -t nat -I OUTPUT -p tcp -o lo --dport 1234 -m state --state NEW -m statistic --mode nth --every 4 --packet 3 -j DNAT --to-destination 127.0.0.1:8083

Wow, this looks amazing. Have you used it for web?

Is this dynamic class execution a common use case? How frequently are you broadcasting new bytecode to your workers?

I just watched your presentation at NWCJS. I was aware that Node was just the ES api implementations on top of v8 and libuv, but your presentation elucidated the exact mechanisms behind the Fly runtime and actually the Node runtime as well.

Seems like y'all are in a good position to expand the native bindings and add some of the more experimental ES proposals faster than Node. Got any details on the Fly roadmap?

Seems they would be happy with the bump?

Sexy as always

This is too expensive and it doesn't even let me take the challenges myself without paying $20AUD, even though is says "Free Trial".

Also, it's basically just 2 forms and some scripts.

It's very quick! Already uninstalled my old app, as it would try to reload every link while on the subway.

Right on! Also, I watched your Compromise presentation and loved it. Thanks again.

Hey, can you provide any insights on working there? I was speaking to a recruiter about working on Gdax and will probably interview in Feb., after I'm out of my current equity hole.