We recently deployed it for one of our clients, who use it to enhance the quality of their government-related customer data. The primary focus is on ensuring compliance with government policies, and it serves as a crucial component in achieving data quality improvements.
External reviews
External reviews are not included in the AWS star rating for the product.
Stands out for its user-friendly interface, robust community support, competitive pricing and strategic approach to improving data accuracy
What is our primary use case?
How has it helped my organization?
The primary advantage revolves around enhancing the quality of the customer's technology through the utilization of Talend Data Quality. By initiating the process with the tool, users can identify and address various data issues through profiling. This proactive approach results in an improvement in data quality, ultimately contributing to more informed and effective decision-making.
What is most valuable?
Its greatest asset lies in its user-friendly interface, specifically within the Talend Open Studio, known for its ease of use and familiarity among users. The robust community support proves invaluable when encountering challenges, providing a reliable resource for issue resolution. Moreover, the pricing structure stands out as highly competitive compared to other offerings in the market, making it a cost-effective choice for users. The most valuable feature lies in the capability to assign data quality issues to different stakeholders, facilitating the tracking and resolution of defective work. This functionality enables a streamlined process for identifying, assigning, and subsequently addressing data quality issues.
What needs improvement?
Talend suite might have a missing product, particularly in the commercial master aspect. This would contribute to completing the overall picture, though the focus isn't necessarily on economic considerations. It would be beneficial to have added a greater openness in the tool, allowing for the presentation of data quality results in alternative tools, which would provide increased flexibility in sharing and utilizing data quality outcomes.
For how long have I used the solution?
I have been working with it for two years.
What do I think about the stability of the solution?
It provides good stability capabilities.
What do I think about the scalability of the solution?
We haven't applied scalability to any existing customer implementations so far.
How are customer service and support?
In terms of the solution's technical support, the interactions were satisfactory, but there is room for improvement, especially in managing expectations. During recent interactions, there was a sense that the support provided fell short of expectations. The support team communicated that a paid service was available for installation and configuration, but other support needs were not adequately addressed. While there is an understanding of the limitations, better assistance could have been provided. On a scale of one to ten, I would rate the support experience at a six.
How would you rate customer service and support?
Neutral
How was the initial setup?
The initial setup proved to be challenging for our team. The challenges were more pronounced when deviating from the default setup, especially when opting for a database other than Postgres. The manual installation process appeared less streamlined, leaving room for improvement in its execution. I remember the team investing at least three to four days in the installation process.
What about the implementation team?
For a relatively straightforward scenario, where a single customer addresses Data Quality from one source, the deployment process follows a strategic approach. Initially, the strategy involves focusing on one source system, with the deployment executed by customer engineers and the Talend tool. The deployment doesn't require an extensive team initially; it relies on adequate resources for the deployment phase. However, even in this streamlined process, collaboration with the customer's team is crucial. The deployment necessitates involving other team members from the customer side to ensure the tool is effectively utilized. The process involves deploying, training, and initiating the setup with the initial system. Subsequently, the customer is empowered to continue and expand the deployment journey autonomously. The entire process can be concluded within a month, contingent upon the active participation of the customer team. However, the timeline isn't solely contingent on technical implementation; a significant factor is the adoption on the customer side. Realistically, substantial results become more apparent between three to six months, a duration influenced by factors such as the size of the customer and the complexity of their processes.
What other advice do I have?
The key to success lies in the adoption of the solution within the customer's processes and services. My recommendation is to initiate the implementation by focusing on critical data. By starting with essential data sets, you can swiftly demonstrate tangible results to the business. This approach is strategic because, often, the technical aspects of the technology are not easily comprehensible to the business stakeholders. Begin with a small yet high-value segment to enhance data quality, and then gradually extend the implementation to cover the entire organization. This phased approach ensures a smoother transition and a more significant impact on overall business processes. Overall, I would rate it eight out of ten.
Comes with a wide library of connects but needs to work on customer support
What is most valuable?
Talend Data integration has a wide library of connectors.
What needs improvement?
The tool's technical support needs to be better. It doesn't have a local data center but pushes everything to the cloud. They need to check in with customers to see if they're happy and how well the solutions work. They need to assign a customer success manager for the accounts they sell.
For how long have I used the solution?
I have been using the product for four and a half years.
What do I think about the stability of the solution?
Talend Data integration's stability is good.
What do I think about the scalability of the solution?
I rate the tools' scalability an eight out of ten.
How was the initial setup?
Talend Data integration's initial deployment is simple.
What other advice do I have?
I rate the product an eight out of ten.
A scalable tool that enables users to write codes and develop custom functionalities
What is our primary use case?
The solution is based on Java. It connects to all available data sources, like APIs, Workday, Salesforce, relational database management systems, Azure, Google Cloud, and AWS. It can do big data processing. It also does batch processing and streaming. It hosts APIs, too. We can consume the queuing mechanisms like Kafka or Java Message Queue.
How has it helped my organization?
We migrated from JD Edwards to SAP. It could have been a very tough transition. However, with the help of Talend, we could do it smoothly. It provided us with connectors that made our job easy.
What is most valuable?
We can develop our own code if we do not see the functionality we need. We can write our own code and call it in the integration pipeline. It is the greatest feature. Once we build JAR, we can run it anywhere we want. We do not need Talend to run it. We can use any third-party scheduler to schedule the job and do a performance check.
What needs improvement?
The vendor successfully created a cloud solution. However, lifting and shifting all the functionality available on-premises will be a heavy task. They are working on it. The product must enhance the data quality. Data lineage features must be integrated seamlessly into the data integration platform.
For how long have I used the solution?
I have been using the solution for more than eight years.
What do I think about the stability of the solution?
I rate the tool’s stability a nine out of ten.
What do I think about the scalability of the solution?
I rate the tool’s scalability a ten out of ten. We can scale it however we want. It's very flexible.
Which solution did I use previously and why did I switch?
We used DataStage and Informatica. We switched to Talend because of its price. It also has a wide range of functionality bundled together. While using Informatica, we had to buy everything separately. DataStage and Informatica charge premium prices. It costs us around 25,000 per license.
How was the initial setup?
The solution is deployed on the cloud. The initial setup is fairly straightforward and self-explanatory.
What was our ROI?
We have seen a return on investment. The solution is easy to deploy. We can deploy it on the JVM servers. We don't need any specific servers to execute the pipelines. People could save a lot of money if they use the tool.
What's my experience with pricing, setup cost, and licensing?
The tool is cheap.
Which other solutions did I evaluate?
We evaluated Airflow. Talend was a better choice.
What other advice do I have?
It's a fairly self-explanatory tool. We get a lot of advice from the community. People must register with the community. It will help them get started very quickly. Overall, I rate the product a nine out of ten.
Provides six important data quality metrics
What is our primary use case?
Talend Data Quality helps me find and fix problems in my data. It checks for errors and follows rules to ensure my data is accurate. If it finds issues, it works together with me and the data stewards to fix them. It is like a team effort to make sure my data is good quality from the start.
How has it helped my organization?
Talend Data Quality made a big difference for our organization. For example, when we were switching from one system to another, and the data in both systems was different, with different rules. When we were moving the data, it was crucial that the quality remained high. Talend Data Quality helped us ensure that the data was accurate and consistent during this transition.
What is most valuable?
The most valuable feature of Talend Data Quality is its ability to provide six important data quality metrics, such as timeliness and discrepancies. It also offers advanced features that allow you to create custom patterns and use regular expressions to identify data issues.
What needs improvement?
In terms of improvement, Talend Data Quality needs better dashboarding. Currently, it provides static PDF reports, which are not very dynamic. It would be more helpful if it offered dynamic dashboards that could be directly used by clients for better analysis.
For how long have I used the solution?
I have been using Talend Data Quality for over seven years.
What do I think about the stability of the solution?
I would rate the stability an eight out of ten.
What do I think about the scalability of the solution?
I would rate the scalability an eight out of ten.
How are customer service and support?
Technical support is good. I would give it a nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have previously used Informatica Data Quality. I switched to Talend Data Quality because it offers more flexibility. It has better connectivity options, including the ability to connect with Apache Hadoop and big data environments, which Informatica couldn't provide.
How was the initial setup?
Deploying Talend Data Quality is not complex. It is based on Java, so once you build it, you can run it easily in various environments. It is that simple.
What's my experience with pricing, setup cost, and licensing?
There are many data quality tools available, but some can be expensive. Talend Data Quality stands out because it is often provided for free if you already have Talend Data Integration, which means you don't need to buy new licenses.
Which other solutions did I evaluate?
What other advice do I have?
My advice to new users is that if you are looking to identify data issues, I would recommend Talend Data Quality as a cost-effective and efficient choice. However, if you also want to enforce rules and handle discrepancies, Talend Data Quality may not be enough, and you should consider Talend's integration solutions for a more comprehensive approach. Overall, I would rate the solution an eight out of ten.
Moderately useful or productive software
High cost and limited functions
1. The cloud has a comprehensive monitoring solution.
2. Database has good administration; all the information is completely organized.
3. ETL/ETL channels can be created and managed easily.
4. Several functions are related; this allows the work to be done much faster.
1. It has very little memory. The speed and performance are very poor.
2. It should have more algorithms, to automatically analyze all the functions that are executed.
3. As several functions are related to each other, there is usually a certain decay when you are performing some type of function individually.
4. Many basic tools have limitations of use.
5. Lastly, it is expensive software.
Allows us to capture large volumes of data from multiple sources and load it to the data lake
What is our primary use case?
We use Talend for the ETL tool data integration. We're using Talend with Spark to capture large volumes of data from multiple sources and load it to the data lake. We're using version 12.
We deploy it in our organization and to our client through AWS as a cloud provider.
We have one IT consultant and 180 people in different technologies, particularly in the data integration side. At least 50% of them know Talend, and some of them know Ab Initio or Informatica.
We may increase usage, but there are more tools coming up in this space, like Kafka real-time integration. Other data integration capabilities are coming up.
How has it helped my organization?
This solution has helped us extract data from various sources and load it into the data lake for our client as a large regional bank.
What is most valuable?
The most valuable feature is the data loading and scripting language. Talend graphs are more user-friendly for developing, modifying, and embedding in business logic.
What needs improvement?
There are some glitches, but mostly they'll fix the ongoing feedback we give to the product guys. However, there could be more enhancements. They're bringing deduplication capabilities to Talend.
I think they should drive toward AI and machine learning. They could include a machine-learning algorithm for the deduplication.
For how long have I used the solution?
5 Years
What do I think about the stability of the solution?
It's stable.
What do I think about the scalability of the solution?
It's scalable.
How are customer service and support?
Technical support is average. I would rate them 3.5 out of 5.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
IBM DatStage, Informatica, and Ab Initio, modern technology is the reason I switched
How was the initial setup?
Installation is straightforward. Deployment only takes a couple of days – maybe a day or two with the infrastructure side. For implementation, you have to write a code in order to get the data.
What about the implementation team?
Deployment can be done in-house if you have dealt with a lot of ETL tools that are integration tools.
What was our ROI?
50% savings in data integration capabilities
What's my experience with pricing, setup cost, and licensing?
The price is on a per-user basis. It's a little more expensive than other tools. There aren't any additional costs beyond the standard licensing fee.
The licensing compared with IBM tools is like 50%.
Which other solutions did I evaluate?
We evaluated Informatica and Ab Initio. We chose Talend because of the data capabilities. It's a better tool for our requirements.
What other advice do I have?
I would rate this solution 8 out of 10.