express-typescript-boilerplate VS Serverless-Boilerplate-Express-TypeScript

You can find more details in my open source boilerplate: https://github.com/ixartz/Serverless-Boilerplate-Express-TypeScript where I'm using TypeScript.

You can check out the GitHub repo for more details at: Node.js Boilerplate with Serverless and Prisma

Here is the link to the Node.js Boilerplate code: https://github.com/ixartz/Serverless-Boilerplate-Express-TypeScript

You can checkout the Serverless Boilerplate Typescript GitHub repo.

As you might know, AWS has recently announced AWS Lambda Function URLs. This is a new feature that allows you to deploy your lambda behind a HTTPS endpoint without API Gateway. So, no need to set up a API gateway with related cost associated to it or add complexity to your serverless architecture for a single lambda function. I'm the author of a Serverless Boilerplate Template that uses Express.js with AWS Lambda. Usually, I got a lot of questions on why I add Express.js to my boilerplate code. Indeed, adding Express.js with API Gateway is redundant and it's not necessary. It'll increase the deployed package size. Now with Lambda Function URLs, you don't need an API Gateway all the time. Without API gateway, all HTTP requests are sending to one lambda function. That means you need a Web framework to handle the request like Express.js. To be clear and avoid any confusion, API gateway is still a solution. But, based on your context and your needs, you can choose to use Lambda Function URLs and remove the API gateway. In the past, a lot of people were suggesting me to remove Express.js from my starter code. Now with Lambda Function, I'm not sure if it's a good idea to remove it from your boilerplate code. What is your thoughts on this?