3 ms·

Seems like many people are not familiar with openresty off which kong is based. https://openresty.org/en/ https://openresty.org/en/ Kong is like an enterpise

Seems like many people are not familiar with openresty off which kong is based. https://openresty.org/en/ https://openresty.org/en/ Kong is like an enterpise version of openresty, i.e nginx turbo-charged with luajit. A lot of really cool and performant things can be built on top of it. At a previous place we wanted to implement an auth & rate limiting ingress to a consul based service discovery. We looked at kong but in the end rolled our own using openresty. No one on the team really liked the ”centralised” approach used by kong. It’s probably preferred in an older schooled enterprise setting tho (awesome project non the less!)

fosk 8y ago
Since Kong 1.0 it can run in both centralized or decentralized mode as a sidecar for Service Mesh. And since v1.1 the database can even be optional. We are executing very fast with the feedback of the community and our customers.
- jordanbeiber 8y ago
  Ah, cool! This was the primary reason for us to custom build. I’ll be starting a new project in a few weeks. Will revisit kong for sure to have a look.
lovehashbrowns 8y ago
I once had to implement a giant ip address blacklist for an api in the fastest and cheapest way possible. Openresty and redis saved me that day. That has been my favorite project that I've ever worked on. Two amazing pieces of software. Kong is great, too. We were just unable to use it because its blacklist feature wasn't easy to implement.
- jordanbeiber 8y ago
  Yeah, great stuff from awesome people! Did not mention it, but of course we used redis to keep track of the rates. :)
- fosk 8y ago
  What problems did you specifically encounter with the current bundled blacklist plugin?
  - lovehashbrowns 8y ago
    This was about 3 years ago. We needed to get millions of IP addresses into the blacklist, with daily updates. We tried using Cassandra for the backed. Not sure if it's easier now but yeah that would have been more of a pain to accomplish.
manish_gill 8y ago
We've been using openresty in production at vwo.com at our edge nodes for quite a few years. It's really fantastic, allowing you to write custom logic and embed it within nginx itself, making things super fast. The only real disadvantage is the lack of a good library ecosystem within lua and openresty. Over the years, as we moved some more logic to edge because $reasons, we ended up rolling our own libs quite a few times. Documentation can be made much easier as well. That, and the occasional limitations of Lua as a language. Overall though, quite an awesome project.
- mikejulietbravo 8y ago
  We love OpenResty! One of our principal engineers was recently named a core maintainer of the project

fosk 8y ago

Since Kong 1.0 it can run in both centralized or decentralized mode as a sidecar for Service Mesh. And since v1.1 the database can even be optional. We are executing very fast with the feedback of the community and our customers.

jordanbeiber 8y ago
Ah, cool! This was the primary reason for us to custom build. I’ll be starting a new project in a few weeks. Will revisit kong for sure to have a look.

lovehashbrowns 8y ago

I once had to implement a giant ip address blacklist for an api in the fastest and cheapest way possible. Openresty and redis saved me that day. That has been my favorite project that I've ever worked on. Two amazing pieces of software. Kong is great, too. We were just unable to use it because its blacklist feature wasn't easy to implement.

jordanbeiber 8y ago
Yeah, great stuff from awesome people! Did not mention it, but of course we used redis to keep track of the rates. :)
fosk 8y ago
What problems did you specifically encounter with the current bundled blacklist plugin?
- lovehashbrowns 8y ago
  This was about 3 years ago. We needed to get millions of IP addresses into the blacklist, with daily updates. We tried using Cassandra for the backed. Not sure if it's easier now but yeah that would have been more of a pain to accomplish.

manish_gill 8y ago

We've been using openresty in production at vwo.com at our edge nodes for quite a few years. It's really fantastic, allowing you to write custom logic and embed it within nginx itself, making things super fast. The only real disadvantage is the lack of a good library ecosystem within lua and openresty. Over the years, as we moved some more logic to edge because $reasons, we ended up rolling our own libs quite a few times. Documentation can be made much easier as well. That, and the occasional limitations of Lua as a language. Overall though, quite an awesome project.

mikejulietbravo 8y ago
We love OpenResty! One of our principal engineers was recently named a core maintainer of the project