An API for my app

My stack for this

1. 01
   Lambda function URLs

   Start here. Free front door, one function per concern.

2. 02
   Neon (serverless Postgres)

   Postgres over HTTP, no VPC or proxy needed.

3. 03
   Lambda Web Functions

   Once it's in your region, move HTTP logic to one Express app with a shared connection pool.

4. 04
   Cloudflare Workers

   In front, if users are global or traffic is huge (auth, rate limits, caching).

Don't

• GraphQL and AppSync

  GraphQL turns your schema into a second product to maintain, and almost no app benefits from it. Plain HTTP endpoints on function URLs do the same job with nothing extra to keep in sync.

  Instead: Lambda function URLs

• API Gateway

  Useful, just not on day one. A function URL already gives you HTTPS, IAM auth, CORS and streaming with nothing else to configure. API Gateway adds routes, stages, deployments and integrations to keep in sync with your code, and a 29–30 second request timeout by default (a function URL allows 15 minutes). Add it when you need what only it does: per-customer API keys and usage plans, request validation, WAF on the endpoint, or writing straight into SQS. Function URLs use the same event format as HTTP APIs, so adding it later changes no code.

  Instead: Lambda function URLs