cloud-nuke VS Kong

- https://gruntwork.io/ - https://github.com/gruntwork-io

After discussing the testing approaches suggested by the two IaC providers Terraform and Pulumi, in the next post we will take a look at the dedicated IaC testing providers takes on this topic. Here we will have a look at Gruntwork and Snyk. So, stay tuned if you are interessted!

Or your working on gruntwork.io company, this is the only the thing that makes ok all what you say here. However I believe they can make better product instead of angry chat on reddit without getting in details.

Like others have said, your infra might itself be the product.

Look at https://gruntwork.io.

They’ve made a lucrative business by selling infra scripts that others can use.

And their subscription model means they keep the scripts up to date.

Have been checking out terragrunt and terratest lately(part of https://gruntwork.io)

Gruntwork | Software Engineers (Principal, Staff) | 100% Remote/US time zones | Full-time | https://gruntwork.io/

We aim to improve humanity's most important invention: Software. Our product enables software teams to launch and maintain production-grade cloud infrastructure in days, not months. We create the building blocks that devs use to make launching in AWS with infrastructure as code 10x better.

We work with AWS, K8s, Terraform, Go, Typescript, and React/Next. We’re a small team (~20 people), but our clients include Toyota, Adobe, TicketMaster, Verizon, and lots of startups.

We are profitable, self-funded (no investors, no debt), pay salaries, equity, and bonuses according to transparent formulas, and are very focused on building a company we're proud of. We are 100% remote, with 2/3 of our team in the USA and 1/3 in Europe. We have company-wide in-person meetups every few months. We welcome applicants from all backgrounds.

Our measure of a successful Grunt is (1) think like an owner, (2) make impact, (3) communicate effectively, (4) be a good person. If this sounds like you, we're hiring!

- Principal Software Engineer

- Staff Software Engineer

Learn more at https://gruntwork.io/careers/

Most people hesitate to use cloud hosted offerings for development. First of all, most providers have a generous free tier for devs, which can get you started. Secondly I recommend using tools like cloudnuke to avoid paying for cloud resources you're not using.

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.