PlayCloudLabs
Sign in
  1. Learn AWS
  2. Architecture
  3. Serverless API

Architecture pattern

AWS Serverless API architecture

when ordinary requests, and nothing to patch

Request in, response out, with compute that exists only for the length of the call. API Gateway handles the front door and auth; Lambda scales with the request rate; DynamoDB keeps the latency flat as the table grows.

What it runs through

In the order a request or a record moves through it. Each one links to the page that explains it.

Signals in a brief that point here

Phrases that, when you meet them in a scenario, mean this shape rather than another. They are the tell, and they are what an exam question is built around.

  • “no operations engineer”
  • “unpredictable traffic”
  • “pay per request”
  • “lookups by key”

What it costs you

Cold starts, a 15-minute ceiling per invocation, and a data model you have to design around the access pattern rather than the entities.

Every shape has one. A design decision with no stated downside is usually a decision nobody has finished making.

Learn the services in it

Shapes it is easily confused with

These run through some of the same services, which is exactly why a brief that fits one can look like it fits another.

Now build it from a brief

Reading a shape and producing one from a scenario that never names a service are different skills, and the exam asks for the second. The scenarios give you the brief; you draw the architecture and it is scored against what the brief requires.

Still there?

You have been away for a while. We have saved what you were working on in this browser. In 60 seconds you will be signed out to keep your account safe.