IBM Cloud Pak for Integration vs Qlik Compose comparison

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

"It is a stable solution."

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

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

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

"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 technical support is very good. I rate the technical support a ten out of ten."

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

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

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

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

"It can scale."

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

"The initial setup is not easy."

"The pricing can be improved."

"Its queuing and messaging features need improvement."

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

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

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

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

"Qlik's ETL and data transformation could be 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."

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

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

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

"It is an expensive solution."

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

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