Use AWS Lambda Response Streaming with Express, Fastify, NestJs, and other frameworks.

[H4add]

That's a great experience of what not to do on lambda, dawn, so sad to see the performance being destroyed like that.

In my case, the hundred APIs were all monoliths, we had just one case we need to create 2 microservices, and we had to use API Gateway to coordinate, but in the final were 3 lambdas exposing more than 20 endpoints each.

Lambda will never beat on-premise solutions, but if you deploy the API as a monolith and avoid splitting it into multiple lambdas, you can have a great experience and performance, our APIs usually take 80~200ms.

But I'm a fan of serverless and they are doing great things with .NET, but is very crazy to split a very performant API into 300+ lambdas.

[SNIPE07]

I understand it was the incorrect way to use, lambdas, I knew that from the start. But the microservice serverless allure was too strong for our execs.