Hevo Data Pipelines
Hevo DataReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
276 reviews
from
External reviews are not included in the AWS star rating for the product.
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
The most stable and quickest solution out there for building data pipelines
What do you like best about the product?
The interface and ease of use. It has got a very slick interface and you can build pipelines literally in less than 5 minutes.
What do you dislike about the product?
The only issue is that the pricing is slightly on the higher end
What problems is the product solving and how is that benefiting you?
It is helping us in building data pipelines for third party sources like google sheets, mixpanel, etc which saves a lot of bandwidth in such cases
Review about Hevo
What do you like best about the product?
There auto setup pipeline, there are only few steps in pipeline set up.
What do you dislike about the product?
a wonderful tool for the pipeline, all set up will be done from hevo team. There is no coding required to set up.
What problems is the product solving and how is that benefiting you?
It helps to get connect any source of data to the database.
Great ETL Provider, With Fabulous Customer Service
What do you like best about the product?
Their customer team is great - and when they can't immediately help you, they keep you up to date with where your question lies, without just sending form response emails.
What do you dislike about the product?
The tool is younger than others, and some standard pipelines are still in Beta or the documentation isn't quite as developed. Overall they're improving day-by-day, but don't expect as much detail readily available.
What problems is the product solving and how is that benefiting you?
Their handling of MongoDb's OpLog
Best ETL I found for MongoDB
What do you like best about the product?
This is the platform with the best usability, having the documentation all time on screen while setting everything is awesome.
How easy it is to connect with MongoDB.
How easy it is to connect with MongoDB.
What do you dislike about the product?
Some fields are named differently in the interface and the documentation.
What problems is the product solving and how is that benefiting you?
This is the best ETL I found to work with MongoDB and JSON Patch.
Helped with prompt solution
What do you like best about the product?
They were able to quickly resolve my issue when the workflow failed.
What do you dislike about the product?
Nothing as of now. The issue was resolved quickly.
What problems is the product solving and how is that benefiting you?
It is solving the problem of maintaining data pipelines, workflows and models which is very critical in my analytics role.
Top-tier quality for mid-tier pricing
What do you like best about the product?
Hevo is extremely easy to use and flexible - it has all the features you could want, including pre and post-load transformations, it's no-code ETL but with the option to code it, and it has a great array of connectors available. It's essentially Fivetran with more features and at a fraction of the price.
What do you dislike about the product?
There are 2 things I dislike: firstly, the destination settings are a bit janky and require you to set up a new database destination every time you want to send data to a different schema. Secondly, the events-based pricing (rather than rows loaded) is annoying and sometimes leads you to quickly use up your quota on connectors you don't really care about. For instance, Facebook and Google Ads involve regular row updates, meaning you have to either set them to very infrequent load schedules (e.g. 24hrs) or move them across to another provider (as in our case).
I wish they gave the option to just not update rows once they're loaded, but overall it's not enough to ruin the experience.
I wish they gave the option to just not update rows once they're loaded, but overall it's not enough to ruin the experience.
What problems is the product solving and how is that benefiting you?
Getting data from A to B in the right format. We've experimented with other tools but this one is by far the most reliable, well-supported and reasonably priced we've come across.
After 6 months of usage, Hevo covered all our needs
What do you like best about the product?
Nice platform, easy to use, with a qualitative documentation, and a very helpful and reactive support
What do you dislike about the product?
Some error messages could maybe be more precise to help understand how to fix our problems, and the ability to track the progress of the ingestion (instead of just ingesting/ingested status)
What problems is the product solving and how is that benefiting you?
We needed to aggregate several data sources to our data warehouse, which Hevo covers perfectly
showing 191 - 200