Kinesis fan-out
0
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?
1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
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.
con risposta 8 anni fa
Contenuto pertinente
AWS UFFICIALEAggiornata 2 mesi fa- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 6 mesi fa