Qlik Compose vs webMethods.io comparison

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

"It is a scalable solution."

"The technical support is very good. I rate the technical support a ten out of ten."

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

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

"It can scale."

"It's a stable solution."

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

"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."

"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."

"webMethods API Portal is overall very valuable. It is now a comprehensive API catalogue that serves various purposes, including API assessment and evaluation."

"I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods."

"ActiveTransfer lets us maintain the file in the staging area before we transfer it. After that, we can remove the file to make sure that the reconciliation process is done. Sometimes we will zip and unzip the files, but if we have a GKB file, we often ignore it."

"One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."

"It is a bundled product stack for A2A and B2B usage. It is one of the best products which I have used during my integration career."

"We needed a tool that was able to orchestrate and help us configure our APIs so that we could maintain and see the heartbeat, traffic, trends, etc."

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

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

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

"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 is some scope for improvement around the documentation, and a better UI would definitely help."

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

"The solution should include REST API calls."

"It is an expensive solution and not very suitable for smaller businesses."

"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."

"Rapid application development has to be considered, especially for UI, where user interference is crucial."

"The product's stability is an area of concern where improvements are required."

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

"The product must add more compatible connectors."

"When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods."

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

"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."

"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."

"The pricing is a yearly license."

"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."

"This is an expensive product and we may replace it with something more reasonably priced."

"Some of the licensing is "component-ized," which is confusing to new users/customers."

"The product is expensive."

"The vendor is flexible with respect to pricing."