Stitch from Talend

Stitch from Talend

Score 8.2 out of 10
Stitch from Talend

Overview

What is Stitch from Talend?

Stitch, or Stitch Data, now from Talend (acquired in late 2018) is an ETL tool for developers; the company was spun off from RJMetrics after that company's acquisition by Magento. Talend describes Stitch as a cloud-first, open source platform for...
Read more

Recent Reviews

A time saver

9 out of 10
January 31, 2018
Stitch is used by the data team which is mainly the BI analyst, the lead developer, the CFO and the web analytics person. We all need the …
Continue reading
Read all reviews
Return to navigation

Product Details

What is Stitch from Talend?

Stitch, or Stitch Data, now from Talend (acquired in late 2018) is an ETL tool for developers; the company was spun off from RJMetrics after that company's acquisition by Magento. Talend describes Stitch as a cloud-first, open source platform for rapidly moving data. It is available on a Free plan, and also a Standard and Enterprise plan which include more advanced features (e.g. an account manager, multiple data destinations, HIPAA compliance, advanced scheduling).

Stitch from Talend Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

 (15)

Attribute Ratings

Reviews

(1-4 of 4)
Companies can't remove reviews or game the system. Here's why
Jono Child | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Stitch is used by the Data team and our Ops teams. The data team uses it for major apis like google ads, Facebook, Salesforce or Intercom to pass data to our warehouse in an easy automated way.

Our Ops team use it to pass data entry from Google sheets to the database to automate tasks or have data for dashboards.
  • Automate data ingestion.
  • Better error messages so you can determine what the problem is.
Stitch is very cheap and useful for small to medium size companies to ingest data from common apis/platforms in a quick and cheap way.
  • Good ROI in terms of being able to monitor cost performance from Google, Facebook, etc.
  • Easy to have Salesforce data and Intercom data for dashboards.
Stitch is much cheaper and probably simpler than tools like Fivetran. Stitch is for simpler projects and used alongside traditional ETL and writing ones own code into APIs.
Fivetran is more of a overarching tool but also more expensive
Score 7 out of 10
Vetted Review
Verified User
We use Stitch, [a Talend company] and Fivetran to ingest data in our snowflake data warehouse. This allows us to allow our users perform ingestion so we can take care of transformations and platform building which are more technical work. We like Stitch's singer based architecture which allows you to extend integration capabilities beyond connectors provided.
  • Easy integration with many sources
  • Extensible
  • Not as expensive as Fivetran
  • Users feel the UI is not as friendly
Ingestion tools make life easy to ingest new data sources. However, they are single tool in your tool box and treat them as such. They won't do your transformations nor do they (neither should they) have ability to define dependencies. They are built for making your ingestions mindlessly simple.
  • Freed up data engineers to work on transformations
  • Bought us some time to migrate from our ETL tool
We use both
Score 7 out of 10
Vetted Review
Verified User
We use Stitch to periodically replicate transactional datastores to an analytics warehouse. The transactional datastore are primarily PostgreSQL and MongoDB databases for microservices. Both the engineering and data teams use Stitch. The transactional datastores are not suitable for running analytics queries; they are tuned for different types of queries and access patterns. Extracting data from the transactional stores, transforming it to a different schema and data types, and loading it into a different datastore is not trivial work, and it is necessary to support the data and BI teams.
  • Stitch is good at replicating relational databases. It manages the conversion of data types and schemas, and it is capable of incremental replication.
  • Stitch's UI makes it easy to configure which tables should be replicated, and how they should be replicated.
  • Stitch is not good at replicating document stores like MongoDB to relational databases. To be fair, this is a difficult task. Stitch flattens the objects, but the result is unwieldy.
  • Stitch cannot replicate the same source to multiple sinks, which is inconvenient if you want to replicate some of a datastore's tables to Redshift and others to Redshift Spectrum, for instance.
Stitch is great for small organizations who want their data and business intelligence organizations to focus on building competitive advantages instead of building data pipelines. AWS DMS offers continuous replication and greater flexibility, if you have the engineering resources to configure it. Stitch may be too inflexible for large organizations with a variety of needs.
  • Stitch manages replication of transactional datastores to our data warehouse. Our data and business intelligence teams need this data to be replicated. Stitch allows our data engineers to focus on our product.
Stitch is less flexible than AWS DMS, but it is fully-managed.
4
Our organization has Stitch users on the data science, engineering, and business intelligence teams.
January 31, 2018

A time saver

Score 9 out of 10
Vetted Review
Verified User
Stitch is used by the data team which is mainly the BI analyst, the lead developer, the CFO and the web analytics person. We all need the data from our third-party tools but do not have the time/skills/will to build and manage integrations.
  • Stitch does one thing and does it well: turn the data ingestion from third-party APIs into a one-click task
  • It makes all that data into a proper schema as a bonus
  • One of our integrations had to be re-synced on a regular basis. I still don't know why.
It is well suited for a startup that does not want to pay a developer/data engineer to develop and monitor third-party API integrations but wants nonetheless to exploit all the insights in the data.

Stitch charges based on the volume of data imported. At some point it is probably cheaper to hire someone to build the integrations in-house.

It is not suited for a big company for which ETL is a really big thing and does not want to outsource it.
  • It has enabled the company to get new insights by joining together datasets that were previously stored in different places.
  • It has saved weeks of work that were used to do more profitable activities than building intregations.
  • It has allowed us to import in the company's data warehouse all the conversations that the customer service agents have had with the customers in case of a potential argument.
The company uses a second ETL tool called Fivetran. They do the same job but have a different set of integrations.

Since with both you pay for what you consume it is worth having the two so you can use the one that gets the better result for a specific API.
I have had some troubles with one integration. It could be solved by doing a full re-sync which is not free. Every time I had to do it, I just sent them an email to tell them that I would do it and they did not charge for it.
No
On a daily basis, I do not have a lot of interaction with Stitch customer service since using the product does not really require any assistance.

The main interaction I had was to ask them not to get charged when doing a full re-sync of one of the integrations. I never had any trouble with this.
Return to navigation