protocol VS Kong

Reserve | Remote | Full-time | https://reserve.org | Censorship resistant money, backed by Peter Thiel and Sam Altman

Early startup with traction, 500k users across three countries, >$100M monthly transaction volume on our financial platform.

Our long-term goal is to offer an alternate currency that is essentially a modernization of commodity money – a cryptocurrency backed by a basket of low-volatility real-world assets. This would provide an alternative to USD that is actually stable enough to use as money. (No, BTC is not the answer. No, algorithmic stablecoins are not the answer.)

We’re open to team members from anywhere, with preference for the Americas due to timezones.

Our github: https://github.com/reserve-protocol/protocol/pulse/monthly

Our public progress tracker for our current protocol implementation: https://bit.ly/3KqFF1F

Open roles:

- smart contracts: https://apply.workable.com/reserve/j/D409ED8CD2/

- front end: https://apply.workable.com/reserve/j/C952B5C3F4/

- back end: https://apply.workable.com/reserve/j/752DE99DC3/

- all other roles: https://reserve.org/jobs/

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.

OPeNsOuRcE. Good time to switch to Kong, better option anyways.

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/

Kong Gateway allows the complexity of service-tier APIs to be reduced to a collection of endpoints (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.

I am seeing different companies taking different approach. I am not sure anymore where each should be actually used. On top of that tech like Kong make me question whether API Gateway should be one thing for all. Some perspective into this would be really appreciated.