SAS Access vs webMethods.io comparison

"The most valuable feature is you have native access to the external databases."

"The most valuable part of SAS/ACCESS is what it is made for: connecting to remote systems that are not part of your physical SAS environment."

"The most valuable aspect of the solution is the ease of access to the data in those databases."

"I like the tool's scalability."

"​Broker and UM are the best features."

"I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well."

"Application integrations are offered out-of-the-box, and that is extremely important to us. This is one of the main use cases that we have for it. It is about 60 to 70 percent of the workload in our application today."

"High throughput and excellent scalability."

"I like the solution's policies, transformation, mediation, and routing features."

"The Software AG Designer has been great. It's very intuitive."

"They are the building blocks of EAI in SAG products, and they offer a very good platform."

"The solution can provide access to the newer databases that come out sooner."

"The pricing model needs to be reconsidered and adjusted."

"I can't really recall any missing feature or general improvement that is needed. We don't really add too many new kinds of databases and therefore our needs are already met."

"The orchestration is not as good as it should be."

"Understanding the overall architecture is difficult."

"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."

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

"The price should be reduced to make it more affordable."

"The initial setup of the webMethods Integration Server is not easy but it gets easier once you know it. It is tiresome but not difficult."

"The market webMethods Integration Server falls under is a very crowded market, so for the product to stand out, Software AG would need to get traction in the open source community by releasing a new version or a base version and open source it, so people can create new custom components and add it to the portfolio."

"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."

"The solution's pricing and licensing are expensive."

"The pricing model is complex and is based on modular packages as well as the size of the applicable environment."

"It is a cost-effective solution."

"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."

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

"Initialy good pricing and good, if it comes to Enterprise license agreements."

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

"The product is very expensive."

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

"Its cost depends on the use cases."