Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

Shards and throughput

This revision card explains Shards and throughput. It starts from the need that too few shards throttle producers; too many waste cost. A shard is a capacity unit (ingest/egress limits). Scale with shard count or on-demand mode. The how-to section notes watch WriteProvisionedThroughputExceeded; split hot shards or use on-demand; pick good partition keys. An example on the card is all events with the same storeId key heat one shard — add more key entropy or split.

Shards and throughput Too few shards throttle producers; too many waste cost. A shard is a capacity unit (ingest/egress limits). Scale with shard count or on-demand mode. Watch WriteProvisionedThroughputExceeded; split hot shards or use on-demand; pick good partition keys. All events with the same storeId key heat one shard — add more key entropy or split.
Shards and throughput · Download PNG
Read card text

What this card says

Why do we need it?

Too few shards throttle producers; too many waste cost.

What is it?

A shard is a capacity unit (ingest/egress limits). Scale with shard count or on-demand mode.

shard

How to do it

Watch WriteProvisionedThroughputExceeded; split hot shards or use on-demand; pick good partition keys.

Example

All events with the same storeId key heat one shard — add more key entropy or split.

See all AWS revision cards