Key points

• Kinesis Data Streams retains records for multiple consumers and replay according to configuration.
• Partition keys determine ordering scope and demand distribution; hot partitions can bottleneck a stream.
• Consumer checkpoint, retry, and idempotency design determines how applications recover.

Best-known use cases

• Process continuous telemetry with multiple consumers.
• Retain an ordered event stream for near-real-time processing and replay.

What candidates often confuse it with

• Kinesis Data Streams provides stream control and replay; Data Firehose provides managed destination delivery.
• Kinesis fits ordered event streams; SQS fits task queues where workers consume queued units of work.

Key takeaway

Choose Kinesis Data Streams when applications need a retained, partitioned stream with custom consumers.

Related services

• Amazon Data Firehose
• Amazon SQS
• AWS Lambda

Relevant exam tasks

• D3.5

Learn more

• Amazon Kinesis