Qlik Compose vs webMethods.io comparison

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

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

"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 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 is a scalable solution."

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

"It's a stable solution."

"webMethods Trading Networks is a stable solution."

"The tool supports gRPC."

"The messaging part is the most valuable feature."

"All of the components are very independent but are tied together to give the business value."

"Most of the work in our organization can be more easily done using the tool."

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

"The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)"

"Best feature is Insight for monitoring, and as a debugging tool. It has saved us a lot of time during crisis situations."

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

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

"I'd like to have access to more developer training materials."

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

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

"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 should be proper documentation available for the implementation process."

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

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

"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."

"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."

"As webMethods Integration Server is expensive, that's its area for improvement."

"The solution should include REST API calls."

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

"The learning curve is a little steep at first."

"Prices should be reduced, ideally by up to 30% for long-term customers 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."

"While they outperform Tableau, there's room for improvement in Qlik's pricing structures, especially for corporate clients like us."

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

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

"Most of my clients would like the price of the solution to be reduced."

"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."

"Some who consider this solution often avoid it due to its high price."

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

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

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