An entire backend on a single lambda would have high cold start times that I would recommend just using fargate if you would rather use containers.
Otherwise I suggest using API Gateway & a lambda per route.
If you want to take a step further into the AWS land I would highly suggest using appsync and VTL templates to have a fully serverless graphql API with 0 lambdas.
My work currently does API Gateway and Lambda approach, but if I could rewrite I would 100% use appsync and VTL templates.
An entire backend on a single lambda would have high cold start times that I would recommend just using fargate if you would rather use containers.
Otherwise I suggest using API Gateway & a lambda per route.
If you want to take a step further into the AWS land I would highly suggest using appsync and VTL templates to have a fully serverless graphql API with 0 lambdas.
My work currently does API Gateway and Lambda approach, but if I could rewrite I would 100% use appsync and VTL templates.
Hey Garret,
What types of start up times do you see and what language are you using?
How is fargate different or better than a Provisioned Concurrency lambda?