Qlik Compose vs webMethods.io comparison

"It can scale."

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

"It's a stable solution."

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

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

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

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

"It integrates well with various servers."

"With webMethods, the creation of servers and the utilization of Trading Networks facilitate B2B integration. It resolves any related issues effectively."

"The solution's ease-of-use is its most valuable feature, in which complex issues may be resolved."

"Currently, we're using this solution for the integration server which helps us to integrate with the mainframe."

"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."

"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."

"Ease of implementation and flexibility to hold the business logic are the most valuable features."

"The stability is good."

"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 believe that visual data flow management and the transformation function should be improved."

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

"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 could be more customization options."

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

"Understanding the overall architecture is difficult."

"We'd like for them to open up to a more cloud-based solution that could offer more flexibility and maybe a better rules engine or more integration with rules engines."

"On the monitoring side of things, the UI for monitoring could be improved. It's a bit cumbersome to work with."

"For code version control, you need to use some external software."

"In terms of improvement, it would be better if it adapted quicker to open standards. It took a while for API specification before the last version was available. The spec of version two was rather quick."

"The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware."

"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."

"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."

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

"The price of the solution is expensive."

"It's a good deal for the money that we pay."

"The pricing is a yearly license."

"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."

"The solution's development license is free for three to six months. We have to pay for other things."

"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."

"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

"It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one."