3 ms·
From what I gather in the GitHub repository, they implement their own L7 management, instead of using NGINX, Envoy, HAProxy, etc. IMO, this adds quite a bit of
by rdli 8y ago
From what I gather in the GitHub repository, they implement their own L7 management, instead of using NGINX, Envoy, HAProxy, etc. IMO, this adds quite a bit of development cost with minimum benefit.
Kong has built on OpenResty (which is built on NGINX), Ambassador has been built on Envoy Proxy -- I think these projects will be able to sustain their velocity more so than projects that need to maintain their own L7 engine. Just watching the speed at which Envoy Proxy is adding stuff is kind of staggering; hard to imagine how another company could do the same on their own homegrown engine.
- jively 8y agoTyk runs its own L7 engine, mainly around primitives provided by the Golang stdlib, IMO having full control over this part provides a lot more flexibility than sitting on top of someone else’s stack, bugs are faster to eke out and optimisation doesn’t rely on upstream code. (Caveat: I’m the CEO of Tyk)
- alain_gilbert 8y agoSorry for asking simple questions. Can someone tell us what exactly is L7 ? It seems like I cannot find any information when googling it.
- alain_gilbert 8y agoFor those interested, "L7 engine" seems to be the "application layer" https://en.wikipedia.org/wiki/Application_layer https://en.wikipedia.org/wiki/Application_layer in the OSI model https://en.wikipedia.org/wiki/OSI_model https://en.wikipedia.org/wiki/OSI_model So communication protocol such as gRPC and HTTP.