sway VS Kong

Fuel Labs | Junior and Senior Software Engineers | Full Time | REMOTE only

Fuel Labs is the blockchain industry leader in scaling R&D and is building Fuel, the fastest execution layer for the modular blockchain stack. We're developing blockchain scaling and smart contract development tools. This includes a new blockchain-optimized high-performance virtual machine (the FuelVM) and a new Rust-based DSL (Sway) for developing safer and more efficient smart contracts.

FuelVM specifications: https://github.com/FuelLabs/fuel-specs

Sway: https://github.com/FuelLabs/sway

If you're interested in working with VMs, interpreters, compilers, end-user-facing toolchains, and/or love good error messages from your compiler, look no further.

We're hiring junior and senior software engineers in Rust, TypeScript, and Solidity. No blockchain experience required; complete disdain for blockchains okay.

https://jobs.lever.co/fuellabs

Sway: https://github.com/FuelLabs/sway

If you're interested in working with VMs, interpreters, compilers, end-user-facing toolchains, and/or love good error messages from your compiler, look no further.

We're hiring junior and senior software engineers in Rust, TypeScript, and Solidity. No blockchain experience required; complete disdain for blockchains okay.

https://jobs.lever.co/fuellabs

Sway is a language developed for the Fuel blockchain. doc: The Sway Programming Language.

Smart contracts, mostly. Rust is used for both compilers and as base for DSLs. For instance Ink is a language built on top of Rust with proc macros, and Sway is a language for smart contracts with a compiler written in Rust.

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.