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

21–30 of 51 posts

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

#21

Post by jively »

polskibus wrote: post #20
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…

Thanks for this comparison, never heard of Tyk before. OT: Your frontpage is very slow (Chrome v.71) - it loads but takes ages to scroll down.

Thanks - we’re painfully aware and are lookig to change it so it’s more usable :-/

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

#22

Post by manigandham »

jively wrote: post #21
polskibus wrote: post #20

Earlier quoted context omitted.

Thanks for this comparison, never heard of Tyk before. OT: Your frontpage is very slow (Chrome v.71) - it loads but takes ages to scroll down.

Thanks - we’re painfully aware and are lookig to change it so it’s more usable :-/

That sky background is a 3MB 1080p video file. Very unnecessary and removing it will fix the problem. Also please remove the scrolling interference, it just makes it hard to continue through the site at my pace.

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

#23

Post by kureikain »

itmeyou wrote: post #13

So I admittedly don't know much about this stuff, but what would be the difference between using Kong and the Nginx ingress controller? What advantages/improvements would I see/be able to use?

Kong is different from Nginx ingress controller. Without a controller, you have to manually register the endpoint/service. You would want to by pass k8s service and use pod ip directly. That's why they do the kong ingress controller.

The main difference is in plugin API. It's very easy to write plugin for Kong. The second is where data is persisted. Kong stores data in db. Therefore they can do something with it. Ingress controller in 0.21 has dynamic backend, they basically hold an in memory objects for api routing rule.

Kong shines when you have complex logic routing, want to leverage their API keys authentication. Such as you can easily expose a service, with API key store in db. Where as you have to write a logs of `auth access` rule and store key in configmap/env in Nginx ingress.

Nginx ingress config is all about watching configmap/annotations and re-generate config. Such as when new service are added, the config is generated(When new pods are added/remove they use Lua to routing so no more reload in there). In Kong, these are seamless, no reload. All data are stored in either Postgres/Cassandra.

That's said, Kong is very nice but it adds more overhead than a simple Nginx ingress.

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

#24

Post by graphememes »

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…

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.

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

#25

Post by sciurus »

jively wrote: post #21
polskibus wrote: post #20

Earlier quoted context omitted.

Thanks for this comparison, never heard of Tyk before. OT: Your frontpage is very slow (Chrome v.71) - it loads but takes ages to scroll down.

Thanks - we’re painfully aware and are lookig to change it so it’s more usable :-/

If nothing else, your site helped me uncover some kind of bug in Firefox's experimental compositor.

https://bugzilla.mozilla.org/show_bug.cgi?id=1515787

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

#27

Post by merlincorey »

vorpalhex wrote: post #19
merlincorey wrote: post #17

Earlier quoted context omitted.

> Nginx gives you the ability to tweak functionality, but it's not as dynamic or as easy out of the box. NginX supports Lua and Javascript embedded and out of the box on many distributions.

That is through a set of additional plugins. Kong uses that base and ships with mature implementing plugins including a robust RESTful API for managing config.

> That is through a set of additional plugins.

Which are compiled and enabled in several distribution packages.

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

#28

Post by hartror »

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…

> you should be able to do all API Management without having to pay us a penny.

I contacted Kong sales once about OpenID connect support, they basically dismissed us as too small. Needless to say we took Kong out of our stack and won't consider it again.

Post reply on HN