Kinesis fan-out

Question

A customer is looking to build a message processing system using Kinesis. This relative low volume (so only one shard will be needed), but low-ish latency is important (<1 sec end-to-end). Currently, there would be four consumers of the stream. However, the expectation is that more consumers would be added in the future.

Do we have best practice guidelines on fanning-out Kinesis streams to multiple consumers?

Accepted Answer

Here is a project on awslabs that uses a AWS Lambda function that accepts messages from an Amazon Kinesis Stream and transfers the messages to another data transport.

https://github.com/awslabs/aws-lambda-fanout

Kinesis fan-out

Relevant content