Qlik Compose vs webMethods.io comparison

"It is a scalable solution."

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

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

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

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

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

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

"It frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."

"The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging."

"Operationally, I consider the solution to be quite good."

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

"High throughput and excellent scalability."

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

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

"We have found the pricing of the solution to be fair."

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

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

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

"There could be more customization options."

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

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

"Technical support is an area where they can improve."

"webMethods.io lacks advanced monitoring and analytics capabilities, so my customers need to use something additional."

"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."

"Understanding the overall architecture is difficult."

"The installation process should be simplified for first time users and be made more user-friendly."

"webMethods Integration Server needs to add more adapters."

"They should develop clear visibility for the onboarding."

"Some things could be improved, especially how ActiveTransfer handles third-party file transfers. It would be nice to have a native file-watching mechanism for when you're scheduling jobs with a third-party scheduler. Currently, we are using an outside file watcher solution to check the files before the file transfer. It checks the location to see if the file is there. If the file is there, it will prepare it for transfer. If the file isn't available, it will send an email it can create a ticket send it now. We recommended adding this file watcher mechanism."

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

"It is a cost-effective solution."

"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."

"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."

"I am not involved in the licensing side of things."

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

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

"The pricing is a yearly license."

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