Qlik Compose vs Talend Data Fabric comparison

"It's a stable solution."

"The technical support is very good. I rate the technical support a ten out of ten."

"One of the most valuable features of this tool is its automation capabilities, allowing us to design the warehouse in an automated manner. Additionally, we can generate Data Lifecycle Policies (DLP) reports and efficiently implement updates and best practices based on proven design patterns."

"I like modeling and code generation. It has become a pretty handy tool because of its short ideation to delivery time. From the time you decide you are modeling a data warehouse, and once you finish the modeling, it generates all the code, generates all the tables. All you have to do is tick a few things, and you can produce a fully functional warehouse. I also like that they have added all the features I have asked for over four years."

"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."

"It can scale."

"Qlik Compose is good enough. It is user-friendly and intuitive."

"It is a scalable solution."

"Talend can be used for multi-cloud purposes, allowing users to orchestrate data across various cloud platforms without purchasing AWS Glue, Azure Data Factory, or similar cloud-specific tools."

"The Talend data integration has been one of the most valuable features."

"We've had no issues with the stability so far."

"The initial setup is very easy."

"It is a smart tool for us to design data pipelines. It lets us populate our three data lake instances. We like this solution for its connection capabilities, since it is very important to be able to use many different types of software. We tested a lot of SAP sources successfully, including cloud sources with SAP. It is also very easy to anonymize data with TIBCO, as well as populating HDFS files, packet files, and raw files. It is very easy to do that with Talend Data Fabric."

"There should be proper documentation available for the implementation process."

"My issues with the solution's stability are owing to the fact that it has certain bugs causing issues in some functionalities that should be working."

"I believe that visual data flow management and the transformation function should be improved."

"When processing data from certain tables with a large volume of data, we encounter significant delays. For instance, when dealing with around one million records, it typically takes three to four hours. To address this, I aim to implement performance improvements across all tables, ensuring swift processing similar to those that are currently complete within seconds. The performance issue primarily arises when we analyze the inserts and updates from the source, subsequently dropping the table. While new insertions are handled promptly, updates are processed slowly, leading to performance issues. Despite consulting our Qlik vendors, they were unable to pinpoint the exact cause of this occurrence. Consequently, I am seeking ways to optimize performance within Qlik Compose, specifically concerning updates."

"There could be more customization options."

"For more complex work, we are not using Qlik Compose because it cannot handle very high volumes at the moment. It needs the same batching capabilities that other ETL tools have. We can't batch the data into small chunks when transforming large amounts of data. It tries to do everything in one shot and that's where it fails."

"It could enhance its capabilities in the realm of self-service options as currently, it is more suited for individuals with technical proficiency who can create pages using it."

"It would be better if the first level of technical support were a bit more technically knowledgeable to solve the problem. I think they could also improve the injection of custom scripts. It is pretty difficult to add additional scripts. If the modeling doesn't give you what you want, and you want to change the script generated by the modeling, it is a bit more challenging than in most other products. It is very good with standard form type systems, but if you get a more complicated data paradigm, it tends to struggle with transforming that into a model."

"We are currently using version 7.3.1, but preferred the version before. The problem that we currently have is that Talend are releasing patches for Talend Studio every quarter. Our technical team has to be on top of these patches and constantly ensure everything is updated."

"I would like to see better integration with other tools."

"Talend's architecture is complex to configure, especially due to the various components involved. It requires a more intricate setup."

"Deployment can be difficult, but I didn't test the latest version yet. With Talend products, every release brings a lot of new features and functionalities. This is never a small adaptation, because the tool is maturing, but we need to test the latest version and to check its deployment capabilities."

"We encounter issues getting email notifications. They should provide enough information about the configuration process for email components."

"While they outperform Tableau, there's room for improvement in Qlik's pricing structures, especially for corporate clients like us."

"The price of the solution is expensive."

"On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six."

"There are multiple subscriptions available with Talend, each with its own scope. Subscriptions depend on the number of users you have and how many remote engines you want to install."

"There are no additional licensing fees when you scale"