Please enable JavaScript.
Coggle requires JavaScript to display documents.
17.198: SQS vs SNS vs Kinesis - Coggle Diagram
17.198: SQS vs SNS vs Kinesis
SQS
Consumer "pull data"
Data is deleted after being consumed
Can have as many worker (Consumers) as we want
No need to provision throughput
Ordering guarantees only FIFO queues
Individual message delay capability
SNS
Push data to many subscribers
Up to 12.5M Sub
Data is not persisted (lost if not delivered)
Pub/Sub
Up to 100K Topic
No need to provision throughput
Integrates with SQS for fan out architecture pattern
FIFO capability for SQS FIFO
Kinesis
Standard: pull data: 2MB/shard
Enhanced fan out: push data: 2MB/shard/consumer
Possibility to replay data
Meant for real time big data, analytics and ETL
Ordering at the shard level
Data expires after 1-365 days
Provisioned mode or on-demand capacity mode