how does it compare to AWS' Application composer?

AWS Application Composer[0], Brainboard[1] and Cloudmaker[2] are a 1:1 mapping tool between a visual representation and an infra-as-code representation. They're more similar to Scratch[3]. You still need to know what to place to get an outcome you're interested in - If you want to set up a globally low latency static web site, or connect an RDS to a Lambda, you still need to figure out CloudFront, custom domains, VPCs, RDS Proxy, draw it all in, etc. And if you were to change RDS into DynamoDB, you'll have to manually undo/reshape the diagram/topology/IaC because some elements no longer make sense or are needed

InfraCopilot is more akin to Wolfram Alpha, in the sense that it has an intelligence/understanding of architecture. You can use high level design to describe your intent and requirements/constraints, and it will deterministically implement it (this isn't LLMs or ChatGPT). When you attempt low level changes, it will validate that they maintain correctness, because it has an understanding of impacts.

When you reshape elements, it has the understanding of follow-on effects, and how to propagate them into the rest of the architecture, all while staying valid.

[0] https://aws.amazon.com/application-composer/

[1] https://www.brainboard.co/

[2] https://cloudmaker.ai/

[3] https://scratch.mit.edu/

Serverless Inc. makes a similar attempt for this: https://www.serverless.com/cloud

There are thousands, if not millions, of developers, now using serverless to build real-life customer-facing applications. As in the whole new tech, it gets adopted for non mission critical apps first between 2016-2018. Starting with 2019, more and more companies adopted the technology and the Cloud providers, especially AWS, invested heavily to improve the integrations and remove the roadblockers. See how Lego has moved the whole e-commerce app into serverless. https://medium.com/lego-engineering/accelerating-with-server...

I also strongly believe that severless is an overloaded term and everyone understands something different from it. Some people consider this only as a FaaS but I think that it's any cloud service, that can auto-scale to infinity, scales to zero, pay-per-use and managed. I frankly believe Serverless should be regarded as a paradigm rather than a technology advancement. here's a very nice blog about it: https://ben11kehoe.medium.com/serverless-is-a-state-of-mind-...

Serverless as a term mixed up with FaaS. In 2022, Serverless is more general as it can be defined anything that autoscales to infinity and scales to zero when not used and pay per use. Amazon DynamoDB is also serverless in that sense for example.

> anything that autoscales to infinity and scales to zero when not used and pay per use

Ah, you mean grid/utility computing. But as you point out that's broader than FaaS.

I don't know what would be the use case for a HTTP endpoint that return 59 minutes later but this seems interesting.

It's for background running tasks. In my company we have functions that process tons of medical records. We call this HTTP function from a cloud task queue, the previous 9 min limit was annoying.

This will make our team happy.

Congrats Or Weis! I have been following Permit.io for a while it's no surprise that your efforts just paid off. Way to go!

Thank you :) Excited to bring easy permissions for everyone.

Not sure if it's what you really want to see but there's a new solution called Serverless Cloud that lets you write only code in JS/TS. This platform handles the infra management itself. It has frontend sync, global CDN, secret management, event-driven design possibilities. https://www.serverless.com/cloud/

Not working for me (Turkey)

The next AWS will be built on AWS, a wise man said one day.

A very nicely curated list. If you're still in search of dealing with cold starts, Thundra also provides a warm-up plugin that helps you keep your serverless functions warm. https://github.com/thundra-io/thundra-lambda-warmup