Kong VS Pizzly

Kong: A cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway or API Middleware). Made available as an open-source project in 2015, its core functionality is written in Lua and it runs on the nginx web server.

Sounds like you want an API gateway? What about Kong?

Unquestionably no, Kong is "OpenResty plus a management plane" and they're Apache 2: https://github.com/kong/kong#license

Kong (https://konghq.com) | Gateway Senior Engineer | REMOTE Europe | Full-time

The Kong Gateway is an API Management solution, which serves as a foundation for many other solutions by the company. The business model is open-core: an Open Source solution exists (https://github.com/kong/kong), and there's an Enterprise version with more features and dedicated support.

The tech stack is a modified Openresty with of Lua code on top. The ideal candidate would be someone who is already familiar with Kong. Alternatively, if you are familiar with Openresty or other API management solution, we also would love to talk with you.

I am personally interested in finding people to join me in the European Gateway Team. The role involves adding features, fixing bugs, and collaborating with other teams. Here's that position:

https://jobs.lever.co/kong/c1a2b204-45a8-4c19-9cd4-d9824a778...

We have many projects and many teams all around the world (current headcount is ~450), using other technologies like Node in the Kong Manager or Go in the Koko project, and we are constantly looking for people. Please visit our careers page to find out more!

https://konghq.com/careers/

The Kong Gateway product allows the complexity of my service-tier APIs to be reduced to a collection of end points (or URIs) focused on meeting a collection of business needs and functionality. Often duplicated components (like authentication, logging, and security) are handled by the gateway and can be removed from the service-tier design. In addition to the common components shown in the original illustration, Kong Gateway offers additional functionality:

However, if your goal is to secure services I would steer towards an API Gateway like Kong.

Kong is built on OpenResty which is NGINX with a Lua JIT.

https://github.com/Kong/kong/issues/484

https://openresty.org/en/

Workaround If you store the access token of the user you should be able to detect if they have already authorized your app and just skip the OAuth flow. OAuth services such as Pizzly or libraries like simple-oauth2 will help you with that (and token refreshes, checking whether the token is expired etc.)

Setting up an OAuth workflow can be somewhat tedious. Luckily, Pizzly offers an amazingly simple way to take care of this. Pizzly provides a proxy server for over 80 OAuth integrations and you can deploy your own instance for free on Heroku (as I did).