Hevo Data Pipelines
Hevo DataReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
263 reviews
from
External reviews are not included in the AWS star rating for the product.
Hevo Data - ETL tool with best support
What do you like best about the product?
The most helpful part is the support for tool which replies within minutes and cooperative
What do you dislike about the product?
It is in developing phase , so lacks some of the required feature like if someone use VPC peering then can't use SSH Tunnel
What problems is the product solving and how is that benefiting you?
We have ETL use case from PSQL to REDSHIFT for which webuse HEVO
The one stop tool for your all data transformations
What do you like best about the product?
Comprehensive and ease of use UI. Support for most of the databases.
What do you dislike about the product?
No proper error messages and UI bugs. Needs more guidance from support team for building pipelines
What problems is the product solving and how is that benefiting you?
Transforming data from NoSQL database to Datawarehouse
Data Integrations made Faster
What do you like best about the product?
How fast we can set up data pipelines, ease of access.
What do you dislike about the product?
More access controls would be helpful and notifications for individual pipelines would be helpful.
What problems is the product solving and how is that benefiting you?
Decreasing the development time and efforts of setting the data pipelines which involves multiple data sources and destinations.
Not a great experience
What do you like best about the product?
Overall, UI, connection and pipeline steps are straightforward and intuitive. We tried mixpanel to data bricks pipelines, creating connection, setting up the pipelines was very easy.
What do you dislike about the product?
For mixpanel to databricks pipeline, we faced a lot of issues in terms of data quality, and billable events. The issues are yet not resolved and I think we kind of did a paid testing for them.
What problems is the product solving and how is that benefiting you?
GUI based drag and drop pipelining for various sources and destinations with the possibility of transformations as well
Best experience among several hosted ETL vendors
What do you like best about the product?
Best entry price point for cost-conscious users. Great UI. Nearly alone in allowing incremental Postgres extractions based on a timestamp column rather than WAL logs. Everything just worked, as advertised.
What do you dislike about the product?
Would like even lower price points for small-data users. We only use about 1/8th of our allowed rows per month, and while HEVO still has the lowest prices of the major vendors for our use case, it could probably be a lot lower.
What problems is the product solving and how is that benefiting you?
We used to use the free Matillion Data Loader product. It was limited in some important ways, but free is a pretty compelling price and it allowed us to paper over the shortcomings with more frequent loads. When the Matillion product switched to paid plans only, we went shopping for the best current product/deal for our use case: syncing several database tables from our operational apps to our Snowflake account. HEVO now fills that role admirably with zero maintenance needs.
Hevo Data is a free application, with good professionals to answer your questions
What do you like best about the product?
Hevo Data presents a very interesting application to work with DW and during my university work in the area of Data Analysis I used this platform and was very well received by the technical team.
What do you dislike about the product?
The platform works well, the ETL process. It would be nice if Oracle DB could run on your platform too.
It would be nice if it could expand to run OLAP, but it has OLAP links to other platforms.
It would be nice if it could expand to run OLAP, but it has OLAP links to other platforms.
What problems is the product solving and how is that benefiting you?
I had difficulties in carrying out the ETL process and they guided me about what was causing the problem.
Hevo has been a useful tool to deploy pipelines between multiple sources/destinations
What do you like best about the product?
The most helpful about Hevo is that you can build pipelines for a wide range variety of sources and sinks with a few clicks, and also it provides a great UI for monitoring those pipelines
What do you dislike about the product?
One of the downsides that I have found using Hevo is that when you surpass your quota and need more records, it becomes expensive, and also, you have a maximum default range
What problems is the product solving and how is that benefiting you?
Hevo is the primary tool that we use to build pipelines to ingest data in our data warehouse, and this is key for our company because we have heavily supported processes with data
Reliable, friendly and fairly priced
What do you like best about the product?
We used Hevo to replicate data from Aurora MySQL and DocumentDB. We had previously evaluated Stitch as an ETL solution but we preferred Hevo for two reasons: it automatically handles schema changes, and it is cheaper.
We had absolutely no issues setting up and the service ran reliably all the time, with ~15 minutes refresh rate.
Support was responsive and resolved our requests successfully in a couple hours.
We had absolutely no issues setting up and the service ran reliably all the time, with ~15 minutes refresh rate.
Support was responsive and resolved our requests successfully in a couple hours.
What do you dislike about the product?
My only gripe with Hevo, and it's a very minor one, is on auto-mapping it prepends table names with the source schema name, which was not desired for our use-case.
Fortunately, there is a workaround by disabling automapping, manually assigning the destination table name, and then reactivating automapping.
This was a minor inconvenience but it would be nice to have the choice to keep the table name only.
Fortunately, there is a workaround by disabling automapping, manually assigning the destination table name, and then reactivating automapping.
This was a minor inconvenience but it would be nice to have the choice to keep the table name only.
What problems is the product solving and how is that benefiting you?
Hevo helps us replicateinto our datawarehouse without having to code and maintain our own pipelines. This allows us to focus on data modelling and analysis instead of worrying about ETL.
Solid tool and improving!
What do you like best about the product?
Hevo integrates with a lot of data sources and destinations, covering everything we need: Amplitude, Google Sheets, MongoDB, PostgreSQL. It's very easy to get started with a new pipeline and to re-run data after initially loading it. Hevo gracefully recovers from errors and re-runs automatically when problems are resolved.
Being able to easily sample events from a given source and re-run those to test pipelines is a nice feature.
Hevo models and workflows are a very simple (and freely offered) implementation of DAGs that allow SQL pipelines to be built... this greatly improved the value we got from Hevo once we started using them.
Being able to easily sample events from a given source and re-run those to test pipelines is a nice feature.
Hevo models and workflows are a very simple (and freely offered) implementation of DAGs that allow SQL pipelines to be built... this greatly improved the value we got from Hevo once we started using them.
What do you dislike about the product?
I wish there was an easier way to manage and re-create pipelines which store the schema mappings. As a result, it is preferable to move configurations into the transformations file, which works fine but I will advise that you do this yourselves so that you're more able to re-create your pipelines as needed.
I believe that sometimes the errors Hevo provides specify the transformed object rather than pre-transformation object. This makes it difficult to debug errors in transformations at times.
The PostgreSQL destination is somewhat slow with Hevo... it would be great if they used the LOAD interface in PostgreSQL (perhaps with necessary restrictions/limitations) prevent this being a bottle neck.
Only being limited to Python2 in the transformations is not ideal. Having access to Python3 or other environments could be powerful as well.
Hevo models are great (see above), but there are certainly limitations with these such as Hevo not being able to manage any changing schemas.
I believe that sometimes the errors Hevo provides specify the transformed object rather than pre-transformation object. This makes it difficult to debug errors in transformations at times.
The PostgreSQL destination is somewhat slow with Hevo... it would be great if they used the LOAD interface in PostgreSQL (perhaps with necessary restrictions/limitations) prevent this being a bottle neck.
Only being limited to Python2 in the transformations is not ideal. Having access to Python3 or other environments could be powerful as well.
Hevo models are great (see above), but there are certainly limitations with these such as Hevo not being able to manage any changing schemas.
What problems is the product solving and how is that benefiting you?
Hevo helps us move data from multiple source systems into our DW, to then transform that data within the DW and keep the tables consumed by BI up to date and clean.
Economic ELT solution with great documentation and support
What do you like best about the product?
Quick implementation of platform and easy to use
What do you dislike about the product?
Should have more dbt based packages like fivetran
What problems is the product solving and how is that benefiting you?
Maintenance of ETL and ELT pipelines and development cost saving
showing 171 - 180