Qlik Compose vs Talend Stitch ETL comparison

"It is a scalable solution."

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

"It can scale."

"I have found it to be a very good, stable, and strong product."

"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."

"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."

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

"As long as you pick the solution that best fits with your requirements, you won't find that performance is a problem. It's good."

"The most valuable feature of Stitch for us is ease of use. This solution is fire-and-forget. All an organization has to do is set up the connection or integration and move on."

"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."

"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."

"Qlik's ETL and data transformation could be better."

"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."

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

"I'd like to have access to more developer training materials."

"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."

"The solution has room for improvement in the ETL. They have an ETL, but when it comes to the monitoring portion, Qlik Compose doesn't provide a feature for monitoring."

"Generally speaking, support is a pain point. In the next release, I would love to see a change in support from the current chat to a more comprehensive portal."

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

"The price of the solution is expensive."

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