[英]In dynamodb, what is the difference between using dynamo streams + lambda trigger versus kinesis streams + lambda trigger?
I am looking into dynamo db streaming options.我正在研究 dynamo db 流选项。 There are 2:
有2个:
Dynamo streams can have a lambda trigger that will consume the stream. Dynamo 流可以有一个 lambda 触发器,它将消耗 stream。
Kinesis streams can also have the lambda trigger that will consume the stream. Kinesis 流也可以有 lambda 触发器,它将消耗 stream。
In both above cases, in the lambda settings we can choose the batch size.以上两种情况,在lambda设置中我们可以选择batch size。
In dynamodb, what is the difference between using dynamo streams + lambda trigger versus kinesis streams + lambda trigger?在 dynamodb 中,使用发电机流 + lambda 触发器与运动流 + lambda 触发器有什么区别?
Below is some of the key differences between Kinesis Data Streams and DynamoDB Streams.以下是 Kinesis Data Streams 和 DynamoDB Streams 之间的一些主要区别。 In regards to your question around a Lambda consumer, the important details to you is data retention, ordering, de-duplication and number of allowed consumers.
关于您关于 Lambda 消费者的问题,对您来说重要的细节是数据保留、排序、重复数据删除和允许的消费者数量。
Properties![]() |
Kinesis Data Streams for DynamoDB![]() |
DynamoDB Streams ![]() |
---|---|---|
Data retention![]() |
Up to 1 year.![]() |
24 hours. ![]() |
Kinesis Client Library (KCL) support ![]() |
Supports KCL versions 1.X and 2.X.![]() |
Supports KCL version 1.X.![]() |
Number of consumers![]() |
Up to 5 simultaneous consumers per shard, or up to 20 simultaneous consumers per shard with enhanced fan-out.![]() |
Up to 2 simultaneous consumers per shard.![]() |
Throughput quotas![]() |
Unlimited.![]() |
Subject to throughput quotas by DynamoDB table and AWS Region.![]() |
Record delivery model![]() |
Pull model over HTTP using GetRecords and with enhanced fan-out, Kinesis Data Streams pushes the records over HTTP/2 by using SubscribeToShard.![]() |
Pull model over HTTP using GetRecords.![]() |
Ordering of records![]() |
The timestamp attribute on each stream record can be used to identify the actual order in which changes occurred in the DynamoDB table.![]() |
For each item that is modified in a DynamoDB table, the stream records appear in the same sequence as the actual modifications to the item.![]() |
Duplicate records![]() |
Duplicate records might occasionally appear in the stream.![]() |
No duplicate records appear in the stream. ![]() |
Stream processing options ![]() |
Process stream records using AWS Lambda, Kinesis Data Analytics, Kinesis data firehose, or AWS Glue streaming ETL.![]() |
Process stream records using AWS Lambda or DynamoDB Streams Kinesis adapter.![]() |
Durability level![]() |
Availability zones to provide automatic failover without interruption.![]() |
Availability zones to provide automatic failover without interruption.![]() |
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.