Live data from Hacker News

Amazon Kinesis Firehose – Simple and Scalable Data Ingestion

aws.amazon.com

11–20 of 33 posts

Re: Amazon Kinesis Firehose – Simple and Scalable Data Ingestion

#11
post #3

Just so I'm understanding, is this a Kafka competitor?

This looks like an AWS version of Apache Flume and Kinesis looks like an AWS version of Apache Storm. Does AWS have a Kafka equivalent i.e. a pub/sub message queue?

Kinesis != Apache Storm The easiest way to think about Kinesis is a managed queue that can remember the history for the past 24 hours.

Re: Amazon Kinesis Firehose – Simple and Scalable Data Ingestion

#15
post #3

Just so I'm understanding, is this a Kafka competitor?

This looks like an AWS version of Apache Flume and Kinesis looks like an AWS version of Apache Storm. Does AWS have a Kafka equivalent i.e. a pub/sub message queue?

Kinesis is a LOT more like Kafka than Storm.

Re: Amazon Kinesis Firehose – Simple and Scalable Data Ingestion

#16
I have a question: if I were to send say 10000 event objects into a Amazon Kinesis Firehose stream it's clear that I should expect them to show up in an S3 bucket of my choosing, but should I also expect that my account will not incur any S3 HTTP POST API request fees ?

Is dodging those HTTP POST fees the value-add over simply using the S3 HTTP API yourself ?

Re: Amazon Kinesis Firehose – Simple and Scalable Data Ingestion

#17
post #11

Earlier quoted context omitted.

This looks like an AWS version of Apache Flume and Kinesis looks like an AWS version of Apache Storm. Does AWS have a Kafka equivalent i.e. a pub/sub message queue?

Kinesis != Apache Storm The easiest way to think about Kinesis is a managed queue that can remember the history for the past 24 hours.

Ah OK. I saw that it kept state so I thought it was like Storm. I don't fully understand Storm. However, Kafka can not keep state (and neither can Flume). So Kinesis is a queue that has some state?

Re: Amazon Kinesis Firehose – Simple and Scalable Data Ingestion

#18

I have a question: if I were to send say 10000 event objects into a Amazon Kinesis Firehose stream it's clear that I should expect them to show up in an S3 bucket of my choosing, but should I also expect that my account will not incur any S3 HTTP POST API request fees ? Is dodging those HTTP POST fees the value-add over simply using the S3 HTTP API yourself ?

Unless I am reading it wrong, it sounds like you need to pay for the requests as well. From https://aws.amazon.com/kinesis/firehose/pricing/:

> Storage

> You will be billed separately for charges associated with Amazon S3 and Amazon Redshift usage including storage and read/write requests. However, you will not be billed for data transfer charges for the data that Amazon Kinesis Firehose loads into Amazon S3 and Amazon Redshift. For further details, see Amazon S3 pricing and Amazon Redshift pricing.

Re: Amazon Kinesis Firehose – Simple and Scalable Data Ingestion

#19
post #6

At Asana, we've been beta testing Kinesis Firehose. It's been quite convenient not having to manage much, and having the data end up in S3. We're also using Kinesis streams, and have a simple KCL app to pull from streams and write to Firehose. We're looking forward to when streams can be as easy to manage, or when we KCL apps can read from Firehose.

I'm confused.. why would you need a KCL app with Firehose (for reading or writing)?
Post reply on HN