4 ms·
We've used this at Patreon to get data from our various sources in the application to Redshift. We've since replaced this with Kinesis Firehose
by lflux 7y ago
We've used this at Patreon to get data from our various sources in the application to Redshift. We've since replaced this with Kinesis Firehose
- mooreds 7y agoAre you still using kafka? Does Kinesis Firehose read from Kafka?
- chrisjc 7y agoNo. If you want to use Firehose, you need to transfer data from Kafka to Kinesis first. You can probably use one of many Kafka Connect Sinks for this. Eg: https://github.com/awslabs/kinesis-kafka-connector https://github.com/awslabs/kinesis-kafka-connector At that point, might as well set up a Kafka Connect cluster with a Kafka Connect Sink, and dump to S3 yourself.
- otterley 7y agoWhy not go whole-hog and use Kinesis Streams and eliminate Kafka altogether?
- chrisjc 7y agoNot sure if you're being factitious, but it sounded like parent's data was already in Kafka. But you're right, no reason not to start with kinesis in the first place, especially with all the AWS options around it including Kinesis Analytics (Streaming "SQL"), Flink (supported by AWS now) or plain old EMR (Spark, Flink, etc...). There is a lot of work that goes into maintaining your own Kafka ecosystem, even if you use Confluent, Lenses, etc...
- lflux 7y agoGood question. Kafka is cheaper for things that don't need to go into redshift, and there's a fair amount of engineering effort that would go in to switching those existing systems over.
- lflux 7y agoWe've phased out Kafka for the parts that feed Redshift, since Kinesis Firehose is a far better experience. We still have Kafka for our application logs and performance monitoring Kinesis Firehose doesn't read from Kafka, we switched our code to publish to Kinesis instead.