dbt is an SQL development environment, developed by Fishtown Analytics, now known as dbt Labs. The vendor states that with dbt, analysts take ownership of the entire analytics engineering workflow, from writing data transformation code to deployment and documentation. dbt Core is distributed under the Apache 2.0 license, and paid Teams and Enterprise editions are available.
N/A
IBM StreamSets
Score 8.2 out of 10
N/A
IBM® StreamSets enables users to create and manage smart streaming data pipelines through a graphical interface, facilitating data integration across hybrid and multicloud environments. IBM StreamSets can support millions of data pipelines for analytics, applications and hybrid integration.
dbt is very flexible and can fit into most data pipelines. This is a pro for most organizations that aren't fully bought into one platform (Google Cloud, etc.)
Matillion is graphical versus dbt, which is SQL code-based (that, of course, is a matter of personal preference and not an objective advantage). The integrated testing, documentation generation, lineage, etc., were additional criteria that led us to choose dbt.
I actually don't know what the alternative to dbt is. I'm sure one must exist other than more 'roll your own' options like Apache Airflow, say, bu tin terms of super easy managed/cloud data transforms, dbt really does seem to be THE tool to use. It's $50/month per dev, BUT …
Snaplogic is great at the Extraction and Load processes of ETL. It can pull data from anywhere, even behind firewalls. So if you need to get data from various APIs, databases, files, S3, SFTP, etc it is easy to do so. However, it requires special knowledge in order to build …
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 …
Airflow can accomplish the same work as dbt (data build tool), however, dbt's (data build tool) development workflow and UI can open up data transformation and modeling work to non-data engineering teams. Looker might also be able to define data models via LookML with a …
First advantage is that this software is particularly new and it keeps updating according to the needs of the user. Other advantage is the it organises and produces conclusions on the basis of data without leaving any relevant information. Other softwares lack in data …
Before, we were using Informatica since most of our applications were running on on-prem servers. Later, when we started moving to the cloud, we tried Informatica Cloud, but it's more useful for batch-oriented than streaming. That's why one of our tech architects suggested IBM …
the IBM solution can be considered a good player in the specific perimeter of application because its main functionalities are working well, are easy to use, and complete. it allows also a good degree of freedom when it comes to personalization of pipelines and streams, and …
We chose IBM StreamSets because we used to own the product before selling it to IBM, so we have a tremendous amount of folks who are familiar with the product.
IBM StreamSets works well when compared to some of the other tools in the same category. They are easy to set up, development can be fast paced as the in-built / out of the box connectors that come along with the product.
StreamSets is a one-stop solution to design Data engineering Pipelines and doesn't require deep Programming knowledge, It's so user-friendly that anyone in Team can contribute to the Idea of pipeline design. In Hadoop One has to be programming proficient to use its various …
dbt (Data Build Tool) is best suited for doing the data transformation. dbt is just a transformation tool and it is not suitable for building a data pipeline which requires extraction of data and loading. dbt is well suited for SQL based transformation logic and it is less appropriate when transformation logic requires python.
Because real-world sources often change (new fields get added, formats get tweaked, etc.), StreamSets helps detect and adapt to those "schema drifts" or changes automatically, or with minimal manual intervention. That makes pipelines more resilient and significantly reduces the maintenance burden. Therefore, data sets with constantly changing sources/formats are great for StreamSets.
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
IBM Stream sets has been a wonderful addition to our technology stack. It has helped in some of our initiatives such as data engineering, data integration for not only external customers but also for internal purposes. The tool has also helped on our use cases related to streaming data. Moving to another tool would require significant amount of work and time.
dbt is very easy to use. Basically if you can write SQL, you will be able to use dbt to get what you need done. Of course more advanced users with more technical skills can do more things.
because i think that overall the solution is having a positive impact on the business, it allows multiple benefits in simplification of the tasks and is capable of doing multiple process that are usually done by a combination of man and systems, reducing the time and effort required to have the data.
Streamsets support has improved a lot in the last couple of years. We had some challenges in the beginning with support, but now the quality of the support and the responsiveness to tickets are better. We have contacted support multiple times when it came to scenarios where the system was slow or the output as not as we expected
Matillion is graphical versus dbt, which is SQL code-based (that, of course, is a matter of personal preference and not an objective advantage). The integrated testing, documentation generation, lineage, etc., were additional criteria that led us to choose dbt.
Before, we were using Informatica since most of our applications were running on on-prem servers. Later, when we started moving to the cloud, we tried Informatica Cloud, but it's more useful for batch-oriented than streaming. That's why one of our tech architects suggested IBM StreamSets for our real-time data streaming. During the POC stage, we were happy that the data streaming was way better with IBM StreamSets compared to the Informatica Cloud way of doing.