anoma VS Kong

COMPANY: Heliax (Project: Anoma)

Heliax | Various Senior Software Engineer | remote or onsite (Zug Switzerland or Berlin) | https://anoma.network

The primary project of Heliax is the Anoma protocol (implemented in Rust). Anoma is a sovereign, proof-of-stake blockchain protocol that enables private, asset-agnostic cash and private bartering among any number of parties. In addition to Anoma, Heliax works on open-source projects which are part of the Anoma ecosystem, including but not limited to research in cryptographic libraries such as the MASP or Ferveo (written in Rust), and tools for high assurance validity predicates and arbitrary zero-knowledge circuits (Juvix, written in Haskell).

Heliax is a remote-first team, currently composed of cross-disciplinary members located around the world. All of our work is open-source. Our work culture is characterized by open-allocation, where team members have a high degree of freedom and autonomy in choosing when to work, what to work on, and whom to work with.

Roles:

Introducing Bandersnatch, a new elliptic curve built over the BLS12-381 scalar field in a paper co-written by Simon Masson, a zero-knowledge cryptography researcher from the team building Anoma. BLS12-381 is a pairing-friendly curve, universally used for digital signatures and zero-knowledge proofs by many projects, one being Anoma.

Anoma. Implementation of the Anoma protocol in Rust. Anoma is a sovereign, proof-of-stake blockchain protocol that enables private, asset-agnostic cash and private bartering among any number of parties. The paper: Anoma: Undefining Money.

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.