3 ms·
turbinelabs.io is the whole of everything we're building on top of nginx/envoy. Our primary goal is to provide more powerful ways to release software like incre
by trjordan 9y ago
turbinelabs.io is the whole of everything we're building on top of nginx/envoy. Our primary goal is to provide more powerful ways to release software like incremental blue/green deploys or canaries or production previews. That requires a solid data plane (nginx/envoy) and management plane (missing in nginx/envoy xDS APIs) underneath it to work. Nobody runs nginx because it's fun -- one of the logical use cases for a better nginx is better releases, which is what we work on.
The transition has been good! There's certainly a lot more complexity to implement with the Envoy APIs, but that's because there's a lot of power. Working with Matt Klein and the rest of the community has been really positive. We're excited about all the other patterns that unlocks, like circuit breaking and tracing. Those sorts of features are on the wrong side of the cost/benefit equation for most companies, but if you get them for free because you deployed Envoy as ingress and service mesh, they're great to have.
- bogomipz 9y agoInteresting thanks for the detailed response. Can you elaborate on your comment about "xDS APIs"? I' not sure which APIs are you referring to.
- trjordan 9y agoThere are 4 Discovery Service APIs that you can implement: service (SDS), cluster (CDS), route (RDS), and listener (LDS). Colloquially called xDS for all of them. https://envoyproxy.github.io/envoy/intro/arch_overview/dynamic_configuration.html https://envoyproxy.github.io/envoy/intro/arch_overview/dynam...
- bogomipz 9y agoI see, I'm looking forward to spending some time looking at envoy. Cheers.