Processing Delay in Kinesis -> Lambda -> DynamoDB

Asked 2 years ago, Updated 2 years ago, 175 views

This is my first time asking a question.


Putting data to Kinesis in AWS Lambda is developing a write to DynamoDB.

The DynamoDB has enough write capacity units, but
Processing speed cannot keep up with data put to Kinesis
The wait time for processing to reflect is getting longer.

Kinesis data is sequential, so it may be obvious, but
There seems to be only one Lambda running at the same time
I think I can solve this problem if the message queue and the worker are one-to-n.
I can't find a way to do it without increasing the Kinesis shard in Kinesis->Lambda...
In the first place, I would like some advice such as using Kinesis incorrectly.
Thank you for your cooperation.

[Operation information]
Kinesis shard count: 1
Put data to Kinesis: 10 to 50 data per second

aws aws-lambda amazon-dynamodb

2022-09-29 22:23

1 Answers

The solution was to write multiple data received by Lambda to Dynamo in parallel.

-- This answer is a community wiki that originally added a self-answer to the question.


2022-09-29 22:23

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.