We performed a comparison between IBM Cloud Pak for Data and Qlik Compose based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Scalability-wise, I rate the solution a nine or ten out of ten."
"The most valuable features are data virtualization and reporting."
"One of Cloud Pak's best features is the Watson Knowledge Catalog, which helps you implement data governance."
"It is a scalable solution, and we have had no issues with its scalability in our company. I rate the solution's scalability a nine out of ten."
"Its data preparation capabilities are highly valuable."
"What I found most helpful in IBM Cloud Pak for Data is containerization, which means it's easy to shift and leave in terms of moving to other clouds. That's an advantage of IBM Cloud Pak for Data."
"The most valuable feature of IBM Cloud Pak for Data is the Modeler flows. The ability to develop models using a graphical approach and the capability to connect to various sources, as well as the data virtualization capabilities, allow me to easily access and utilize data that is dispersed across different sources."
"You can model the data there, connect the data models with the business processes and create data lineage processes."
"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."
"There were many valuable features, such as extracting any data to put in the cloud. For example, Qlik was able to gather data from SAP and extract SAP data from the platforms."
"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."
"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."
"It can scale."
"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."
"I have found it to be a very good, stable, and strong product."
"The interface could improve because sometimes it becomes slow. Sometimes there is a delay between clicks when using the software, which can make the development process slow. It can take a few seconds to complete one action, and then a few more seconds to do the next one."
"The solution could have more connectors."
"The tool depends on the control plane, an OpenShift container platform utilized as an orchestration layer...So, we have communicated this issue to IBM and asked if it is feasible to adapt the solution to work on a Kubernetes platform that we support."
"The product is trying to be more maturity in terms of connectors. That, I believe, is an area where Cloud Pak can improve."
"There is a solution that is part of IBM Cloud Pak for Data called Watson OpenScale. It is used to monitor the deployed models for the quality and fairness of the results. This is one area that needs a lot of improvement."
"Cloud Pak would be improved with integration with cloud service providers like Cloudera."
"One challenge I'm facing with IBM Cloud Pak for Data is native features have been decommissioned, such as XML input and output. Too many changes have been made, and my company has around one hundred thousand mappings, so my team has been putting more effort into alternative ways to do things. Another area for improvement in IBM Cloud Pak for Data is that it's more complicated to shift from on-premise to the cloud. Other vendors provide secure agents that easily connect with your existing setup. Still, with IBM Cloud Pak for Data, you have to perform connection migration steps, upgrade to the latest version, etc., which makes it more complicated, especially as my company has XML-based mappings. Still, the XML input and output capabilities of IBM Cloud Pak for Data have been discontinued, so I'd like IBM to bring that back."
"The technical support could be a little better."
"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."
"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."
"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."
"Qlik's ETL and data transformation could be better."
"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."
"I'd like to have access to more developer training materials."
"There could be more customization options."
IBM Cloud Pak for Data is ranked 15th in Data Integration with 11 reviews while Qlik Compose is ranked 20th in Data Integration with 12 reviews. IBM Cloud Pak for Data is rated 8.0, while Qlik Compose is rated 7.6. The top reviewer of IBM Cloud Pak for Data writes "A scalable data analytics and digital transformation tool that provides useful features and integrations". On the other hand, the top reviewer of Qlik Compose writes "Easy matching and reconciliation of data". IBM Cloud Pak for Data is most compared with IBM InfoSphere DataStage, Azure Data Factory, Informatica Cloud Data Integration, Palantir Foundry and Denodo, whereas Qlik Compose is most compared with Qlik Replicate, Talend Open Studio, Azure Data Factory, SSIS and Palantir Foundry. See our IBM Cloud Pak for Data vs. Qlik Compose report.
See our list of best Data Integration vendors.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
