Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kong gateway reaches 1.0 GA, now supports service mesh

konghq.com

Post reply on HN
Print view View original

31–40 of 51 posts

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#31

Post by fortuneandglory »

graphememes wrote: post #24
jively wrote: post #18

Earlier quoted context omitted.

(Caveat: I’m the CEO of Tyk) Tyk offers a more “batteries included” approach to Kong, and so doesn’t rely on external plugin authors to extend the ecosystem. 100% of our dev team are constantly working on our open source components and we like to keep it that way. Because of that, Tyk isn’t “open core” like Kong is, there’s no lock-in or levers to get you to buy our value-adds like our Management Dashboard GUI or our…

I've used both, Kong is more "pluggable" and easier to extend in my experience. Also, the ecosystem and community around Kong is much stronger than Tyk's which is amazing.

I'd argue Tyk is easier to extend Tyk, as they include many plugins already baked-into their OS gateway. If you want to extend Kong with some custom plugins I think Lua is your only option. With Tyk you can use pretty much any programming language to write your middleware. Gets my vote

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#32

Post by bullen »

jklepatch wrote: post #30

I used Kong in a project recently. Very bare-bones, You need to build your own client for it. Overall, it felt like a blackbox where things magically happened. Totally hated it.

What about performance, did you use it so much you got a sense of that? To me there is nothing that beats haproxy so far.

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#33

Post by fosk »

jklepatch wrote: post #30

I used Kong in a project recently. Very bare-bones, You need to build your own client for it. Overall, it felt like a blackbox where things magically happened. Totally hated it.

Hello, CTO of Kong here. You mean a client to consume the Admin API in order to create entities on Kong? If that's the case the community has built lots of open source clients in pretty much any language that would make the job of integrating Kong within an existing system much easier. The community around Kong has also built declarative configuration support that you can use instead of the Admin API.

Our official declarative configuration will also be released very soon, and in some environments (like Kubernetes) we already support it.

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#34

Post by mikejulietbravo »

bullen wrote: post #32
jklepatch wrote: post #30

I used Kong in a project recently. Very bare-bones, You need to build your own client for it. Overall, it felt like a blackbox where things magically happened. Totally hated it.

What about performance, did you use it so much you got a sense of that? To me there is nothing that beats haproxy so far.

They are different products. Nginx and haproxy are more comparable. If you like HAproxy as a load balancer, you can easily use it with Kong. A lot of people do just that.

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#35

Post by fosk »

nphase wrote: post #16

How does Kong compare to Tyk?

Hello, Marco CTO of Kong here.

Kong is arguably more popular than Tyk (and other similar gateways) when it comes to adoption (55M+ downloads and more than 70,000 instances of Kong running per day across the world), and faster when it comes to performance. BBVA - a large banking group - wrote this technical blog post a while ago comparing Kong's and Tyk performance: https://www.bbva.com/en/api-gateways-kong-vs-tyk/\

Kong OSS is 100% open source, not limited to non-commercial use.

Kong is basically a programmable runtime that can be extended with Plugins [1]. There are more than 500+ plugins that are available on GitHub that we are (slowly) adding to the official Hub, among over 5000+ contributions. You can talk to the community at https://discuss.konghq.com/

Kong is also lightweight with a lower footprint, which is required to support both traditional API gateway use cases and modern microservices environments (Kubernetes sidecar, for example). Because of that, our users are basically using one runtime for both N-S traffic (traditional API Gateway usage) and E-W traffic within a microservice oriented architecture. You can easily separate data and control planes to grow to thousands of Kong nodes running in a system.

There are users/customers running 1M+ TPS on top of distributed Kong clusters spanning across different platforms (containers, multi-cloud, even bare metal) with less than As a result to Kong's adoption, the business is also growing very rapidly which will allow us to better deliver OSS features moving forward :) [2]

You can ping me at https://twitter.com/subnetmarco

[1] https://docs.konghq.com/hub

[2] https://konghq.com/about-kong-inc/kong-hits-record-growth-20...

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#36

Post by vaseem »

fosk wrote: post #33
jklepatch wrote: post #30

I used Kong in a project recently. Very bare-bones, You need to build your own client for it. Overall, it felt like a blackbox where things magically happened. Totally hated it.

Hello, CTO of Kong here. You mean a client to consume the Admin API in order to create entities on Kong? If that's the case the community has built lots of open source clients in pretty much any language that would make the job of integrating Kong within an existing system much easier. The community around Kong has also built declarative configuration support that you can use instead of the Admin API. Our official de…

I am surprised you did not try to upsell Enterprise version

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#37

Post by fosk »

vaseem wrote: post #36
fosk wrote: post #33

Earlier quoted context omitted.

Hello, CTO of Kong here. You mean a client to consume the Admin API in order to create entities on Kong? If that's the case the community has built lots of open source clients in pretty much any language that would make the job of integrating Kong within an existing system much easier. The community around Kong has also built declarative configuration support that you can use instead of the Admin API. Our official de…

I am surprised you did not try to upsell Enterprise version

It is a community product first and foremost with a plugin framework that allows for extensibility with access to the full core API.

You can discuss with the community online [1], or meet a core contributor at one of the community meetups or in the monthly community call that we usually announce on Discuss.

[1] https://github.com/Mashape/kong or https://discuss.konghq.com/

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#38

Post by bungle »

jively wrote: post #18
nphase wrote: post #16

How does Kong compare to Tyk?

(Caveat: I’m the CEO of Tyk) Tyk offers a more “batteries included” approach to Kong, and so doesn’t rely on external plugin authors to extend the ecosystem. 100% of our dev team are constantly working on our open source components and we like to keep it that way. Because of that, Tyk isn’t “open core” like Kong is, there’s no lock-in or levers to get you to buy our value-adds like our Management Dashboard GUI or our…

Kong has an OpenID Connect plugin that comes with Enterprise, but there are at least three OpenID Connect plugins made by the community, one of them is from Nokia.

I work for Kong and I am an author of that enterprise OpenID Connect plugin. Maybe that is a biggest exception to me, as otherwise I'd say that almost all of my code and related goes directly to OSS.

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#39

Post by wavesquid »

Hi all,

I was the lead developer on the service mesh implementation. I've just pushed https://github.com/Kong/kubernetes-sidecar-injector public, which should make deploying kong a service mesh simple on kubernetes.

Let me know if you have any questions, I'll try and check over the next few days.

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#40

Post by xiaomai »

fosk wrote: post #33
jklepatch wrote: post #30

I used Kong in a project recently. Very bare-bones, You need to build your own client for it. Overall, it felt like a blackbox where things magically happened. Totally hated it.

Hello, CTO of Kong here. You mean a client to consume the Admin API in order to create entities on Kong? If that's the case the community has built lots of open source clients in pretty much any language that would make the job of integrating Kong within an existing system much easier. The community around Kong has also built declarative configuration support that you can use instead of the Admin API. Our official de…

Excited to hear about an official declarative config. When we were looking at deploying Kong, this was our biggest pain point (looked at lots of 3rd party solutions but none were ideal).
Post reply on HN