dbt vs. Hevo Data

If you can load your data first into your warehouse, dbt is excellent. It does the T(ransformation) part of ELT brilliantly but does not do the E(xtract) or L(oad) part. If you know SQL or your development team knows SQL, it's a framework and extension around that. So, it's easy to learn and easy to hire people with that technical skill (as opposed to specific Informatica, SnapLogic, etc. experience). dbt uses plain text files and integrates with GitHub. You can easily see the changes made between versions. In GUI-based UIs it was always hard to tell what someone had changed. Each "model" is essentially a "SELECT" statement. You never need to do a "CREATE TABLE" or "CREATE VIEW" - it's all done for you, leaving you to work on the business logic. Instead of saying "FROM specific_db.schema.table" you indicate "FROM ref('my_other_model')". It creates an internal dependency diagram you can view in a DAG. When you deploy, the dependencies work like magic in your various environments. They also have great documentation, an active slack community, training, and support. I like the enhancements they have been making and I believe they are headed in a good direction.

Incentivized

It is of great help for unstructured data sources. The way Hevo Data flattens the high nested data is amazing. Schema management is also good by Hevo Data. The way it's tell about the data type and then we can identify any error in the model. Additionally, It is very easy to setup for any new user and once model is created then we do not have to worry about the script maintenance and updating the script daily.

Incentivized

• user experience makes it easy to work with SQL and version control
• customer success team and the dbt (data build tool) community help establish best practices
• thorough and clear documentation

• Hevo is the best tool when you want to manage a large number of pipelines. With Hevo you can automate the pipelines very easily.
• Hevo's great features are automatic detection and notification of failed data pipelines.
• Auto mapping feature is also good. It's makes really easy to move the data.
• Integration is easy with so many databases like SQL, Google Sheet, etc.

Incentivized

• Slow load times of the dbt cloud environment (they're working on it via a new UI though)
• More out-of-the-box solutions for managing procedures, functions, etc would be nice to have, but honestly, it's pretty easy to figure out how to adapt dbt macros

Incentivized

• Transformation
• More Sources
• More Destinations

Incentivized

Most ETL pipeline products have a T layer, but dbt just does it better. The transformation is on steroids compared to the others. Also, just allows much more Adhoc solutions for very specific projects. Those ETL tools are probably better on the T part if you don't need too many transforms - also dbt is pretty much free dependent on how you work it, also extremely scalable.

Incentivized

Much lower cost and faster syncs but not as good support. More flexible in terms of pricing, though. Fivetran requires annual contracts and is very inflexible.

Incentivized

• Simplified our BI layer for faster load times
• Increased the quality of data reaching our end users
• Makes complex transformations manageable

Incentivized

• Comprehensive results from the data processing is a perfect approach from the tool.
• Authentic data models brings a high automation process and more productivity.
• Expansive data sourcing brings clarity and genuine results after inferential analytics.

Incentivized