BizTalk Server vs webMethods.io comparison

"I rate the tool's stability a nine out of ten."

"Compared to the current solutions I use, like Azure Logic Apps and other cloud services, BizTalk was far better and more reliable."

"We can handle a large number of messages without any issues, ensuring that everything runs smoothly."

"BIzTalk's integration with Visual Studio is the most valuable feature of this product."

"Essentially, you can do whatever you like with these systems, and you do not have to take care about the scaling because if one server is overloaded, it just forwards the message to the next server, even if it were designated to a specific server. It weeds out the messages according to the load. If you want to scale it, you just add new servers."

"The AS2 communication protocol is one of the most advanced processes."

"The most valuable feature is its reliability and stability. The first version of BizTalk was released in 2000, and many companies still use it. It was stable until 2013 when we had support."

"The most valuable feature of BizTalk Server is that it will turn XML into flexible transactions."

"The tool is very powerful and user-friendly."

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

"The stability is good."

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

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

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

"There were no complexities involved in the setup phase...The product is able to meet my company's API protection needs."

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

"The deployment could be simplified."

"BizTalk Server is an outdated legacy system that does not support messaging."

"BizTalk is in the past, Microsoft is not going to evolve it any further or add any new features."

"The product could be improved in monitoring, managing, and support functionalities."

"The product's deployment can be quicker"

"It's a complex product because you have many degrees of freedom to connect different parts together. Whether it's sensible or not, is up to you, but the machine does allow it. But because of the vast degrees of freedom, it's complex."

"Updating things in BizTalk is a headache."

"BizTalk lacks native cloud support. BizTalk doesn't offer in-built support for cloud. We need to use third-party adapters to connect it to cloud services."

"I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier."

"webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience."

"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."

"The solution's release management feature could be better."

"The high price of the product is an area of concern where improvements are required."

"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."

"The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. For how long"

"Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion."

"It was not cheap, but it was affordable."

"BizTalk Server is not freeware. There's a significant licensing cost involved. Be sure you will actually utilize its features fully."

"BizTalk Server is cheap. I would rate its pricing a two out of five."

"Based on the knowledge, it is relatively cheaper than Azure Identity Services and cloud services in general."

"The solution is expensive."

"The cost will depend on the client's requirements."

"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."

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

"There is a license needed to use the webMethods Integration Server."

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

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

"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."

"I would like to see better pricing for the license."

"The pricing is a yearly license."