IBM Cloud Pak for Integration vs Qlik Compose comparison

"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."

"It is a stable solution."

"Cloud Pak for Integration is definitely scalable. That is the most important criteria."

"The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."

"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."

"It is a scalable solution."

"It can scale."

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

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

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

"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's a stable solution."

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

"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."

"Enterprise bots are needed to balance products like Kafka and Confluent."

"The initial setup is not easy."

"The pricing can be improved."

"Its queuing and messaging features need improvement."

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

"There is some scope for improvement around the documentation, and a better UI would definitely help."

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

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

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

"There could be more customization options."

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

"It is an expensive solution."

"The solution's pricing model is very flexible."

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

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