29 ms·
To avoid interference between user application and theirs? Kinesis has pretty delicate throttle per shard and having user application that is out of their contr
by cherioo 11y ago
To avoid interference between user application and theirs? Kinesis has pretty delicate throttle per shard and having user application that is out of their control working off the same shard will probably make the Firehose part much more fragile.
If you're already doing all the Kinesis shard management/KCL willy nilly why not just dump it to S3 yourself? Firehose seems to be targeting users who don't want to deal with sharding.
- nivertech 11y agoYes, I figured out that Firehose is more higher-level product, than Kinesis. Maybe in the future it will be extended with API to read from a delivery stream. There are competing products, like Google Cloud Pub/Sub where there is no need to manage shards manually or run your own workers, like KCL.