PlayCloudLabs
Sign in
  1. Learn AWS
  2. Architecture
  3. Streaming telemetry

Architecture pattern

AWS Streaming telemetry architecture

when many devices sending small messages constantly

A stream, not a queue: the same records are read by several consumers independently and can be replayed. One consumer keeps the current state for dashboards, another writes history to S3 for analytics, a third watches for thresholds and alerts.

What it runs through

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

  1. Kinesis Data StreamsAmazon Kinesis Data Streams
  2. LambdaAWS Lambda
  3. DynamoDBAmazon DynamoDB
  4. S3Amazon S3

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.

  • “millions of devices”
  • “every few seconds”
  • “near real time”
  • “alert on a threshold”
  • “historical analysis”

What it costs you

Shards are yours to size, and a hot partition key will bottleneck the whole stream.

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.