Senior Data Engineer Consultant at a tech company with 201-500 employees
Real User
Top 10
2023-03-01T14:40:00Z
Mar 1, 2023
Cloud services are often cheaper in the beginning, but when the amount of data and needed resources grows, they cost more and more. In my opinion, it is sometimes simpler to use an existing service rather than having to maintain our own internal infrastructure. This way, we can focus on the things we are good at and can make money from, rather than having to employ people to support the infrastructure. In general, cloud services are very convenient to use, even if we have to pay a bit more, as we know what we are paying for and can focus on other tasks. However, if the scale is large, I would consider making changes depending on the situation.
The solution is costly. There is a fee to activate the service and even if it is not being used there is a monthly fee because they continue to maintain the service. If we want to retain the data for longer durations then we are charged the equivalent of Amazon S2 or S3 services. The fee is based on the number of hours the service is running.
Chief Technology Officer at a tech services company with 51-200 employees
Real User
2021-08-25T19:54:29Z
Aug 25, 2021
The solution's pricing is fair. The trick lies in Amazon's pricing. They charge according to the different layers of or types of data that is transfered.
Senior Software Engineer at a tech services company with 501-1,000 employees
Real User
2020-12-21T13:55:00Z
Dec 21, 2020
I think there is a paid version only, there is no free version. I think it is possibly on the expensive side. I did not go too deep into pricing, because our business did not care about pricing that much. They just wanted the product to be solid and level at all times. The business is generally conservative about services and pricing. But, this was a different case for us where the price did not matter. I did not explore that much into the pricing of Kinesis, per se.
The pricing depends on the number of shards that we are providing and the time the application is running. We reduced the cost of the pipeline that we built. We built a generic type of pipeline so that two more times can use same data pipeline.
In terms of the prices, I think it is a fair price. Kinesis Data Stream has a very fair price relative to the value that it provides. Same for Firehose. As for Kinesis Analytics, I find it on the more expensive side because it's a newer component, something fewer people use, and something more innovative, cutting edge, and more specific. I would say Analytics is more on the expensive side of the spectrum. I would say that Kinesis Analytics is the only one that I may complain about if you like low pricing.
Principal Data Engineer at a transportation company with 1,001-5,000 employees
Real User
2020-10-15T11:35:04Z
Oct 15, 2020
I would say pricing is really great. If pricing is an issue, I'd definitely recommend Kinesis because our Kinesis costs are under $1,000 a month. The product is super cost effective and it's the same with the licensing. Compared to Google Cloud and Azure, they're probably pretty similarly priced. I wouldn't say you're going to get a huge benefit going to Kinesis, but if you're considering using Kafka or another solution that's not hosted, it's not really worth all the effort when you could just go with a managed solution. It's a lot better cost-wise.
Amazon Kinesis makes it easy to collect, process, and analyze real-time, streaming data so you can get timely insights and react quickly to new information. Amazon Kinesis offers key capabilities to cost-effectively process streaming data at any scale, along with the flexibility to choose the tools that best suit the requirements of your application. With Amazon Kinesis, you can ingest real-time data such as video, audio, application logs, website clickstreams, and IoT telemetry data for...
The product falls on a bit of an expensive side.
The solution is cheap.
The tool's entry price is cheap. However, pricing increases with data volume.
The price is not much cheaper, but I can't say it's too expensive either. However, the customers do not have to pay any additional costs.
Cloud services are often cheaper in the beginning, but when the amount of data and needed resources grows, they cost more and more. In my opinion, it is sometimes simpler to use an existing service rather than having to maintain our own internal infrastructure. This way, we can focus on the things we are good at and can make money from, rather than having to employ people to support the infrastructure. In general, cloud services are very convenient to use, even if we have to pay a bit more, as we know what we are paying for and can focus on other tasks. However, if the scale is large, I would consider making changes depending on the situation.
The solution is costly. There is a fee to activate the service and even if it is not being used there is a monthly fee because they continue to maintain the service. If we want to retain the data for longer durations then we are charged the equivalent of Amazon S2 or S3 services. The fee is based on the number of hours the service is running.
It was actually a fairly high volume we were spending. We were spending about 150 a month.
The solution's pricing is fair. The trick lies in Amazon's pricing. They charge according to the different layers of or types of data that is transfered.
I think there is a paid version only, there is no free version. I think it is possibly on the expensive side. I did not go too deep into pricing, because our business did not care about pricing that much. They just wanted the product to be solid and level at all times. The business is generally conservative about services and pricing. But, this was a different case for us where the price did not matter. I did not explore that much into the pricing of Kinesis, per se.
The pricing depends on the number of shards that we are providing and the time the application is running. We reduced the cost of the pipeline that we built. We built a generic type of pipeline so that two more times can use same data pipeline.
In terms of the prices, I think it is a fair price. Kinesis Data Stream has a very fair price relative to the value that it provides. Same for Firehose. As for Kinesis Analytics, I find it on the more expensive side because it's a newer component, something fewer people use, and something more innovative, cutting edge, and more specific. I would say Analytics is more on the expensive side of the spectrum. I would say that Kinesis Analytics is the only one that I may complain about if you like low pricing.
I would say pricing is really great. If pricing is an issue, I'd definitely recommend Kinesis because our Kinesis costs are under $1,000 a month. The product is super cost effective and it's the same with the licensing. Compared to Google Cloud and Azure, they're probably pretty similarly priced. I wouldn't say you're going to get a huge benefit going to Kinesis, but if you're considering using Kafka or another solution that's not hosted, it's not really worth all the effort when you could just go with a managed solution. It's a lot better cost-wise.