Try our new research platform with insights from 80,000+ expert users

BizTalk Server vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 27, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

BizTalk Server
Ranking in Business-to-Business Middleware
8th
Average Rating
7.4
Reviews Sentiment
6.4
Number of Reviews
13
Ranking in other categories
Process Automation (16th)
webMethods.io
Ranking in Business-to-Business Middleware
3rd
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
92
Ranking in other categories
Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), API Management (10th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
 

Mindshare comparison

As of March 2025, in the Business-to-Business Middleware category, the mindshare of BizTalk Server is 4.2%, up from 2.7% compared to the previous year. The mindshare of webMethods.io is 9.4%, up from 7.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Business-to-Business Middleware
 

Featured Reviews

Srinidhi S - PeerSpot reviewer
For production environments, messages are easily stored within the MessageBox database and offers multiple deployment methods
Some room for improvement means... it's legacy. It's an on-premises system, requiring physical servers for deployment. This is different from Azure; you don't need any servers with Azure. If you have a subscription, you can do whatever you want. There are unit restrictions based on the environment (like non-production vs. production) in BizTalk. You need physical servers and databases. In Azure, those are not required – it's all in the cloud. Now, we have the option of integrating accounts and the On-Premises Data Gateway to connect on-premises BizTalk with Azure. But the trend is moving towards Azure. Not everyone wants a hybrid model. Companies are still going with hybrid scenarios, but they want both BizTalk and Azure. See, whatever you can do in BizTalk, you cannot do the same things the same way in Azure. One example is tracking. In BizTalk, especially for production environments, messages are easily stored within the MessageBox database. Support can assist in retrieving them directly. It's not as easy to track in Azure – everyone can potentially access it, and even reprocessing is different. Logic Apps have a preview mode. If a Logic App is stuck at a particular action, you can resubmit from there. Microsoft is still making improvements – I don't know when they'll have general availability for these features. However, tracking and message storage are more complex in Azure. We have to use Azure Blob storage for archiving, whereas in BizTalk, it's a built-in feature of the MessageBox DB. If you need to debug at any point, you can do so easily in BizTalk. This is one aspect influenced by the on-premises nature of BizTalk. Since everything is moving to the cloud, Microsoft will also end support for BizTalk Server 2030 – there won't be any further support. I don't think they'll release any new versions. 2020 was the last, and it's been four years. After the end of support, I think companies currently using BizTalk will move to Azure or another cloud-based integration technology.
Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature of BizTalk Server is that it will turn XML into flexible transactions."
"The tool's most valuable feature is its integration with the banks. Its messaging and routing capabilities are good."
"We can handle a large number of messages without any issues, ensuring that everything runs smoothly."
"Compared to the current solutions I use, like Azure Logic Apps and other cloud services, BizTalk was far better and more reliable."
"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."
"I rate the tool's stability a nine out of ten."
"BIzTalk's integration with Visual Studio is the most valuable feature of this product."
"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."
"It's a visual tool, so our transformations can be quickly implemented without a lot of fuss. The fact that we have an easy way to expose REST services is also very interesting. It offers the possibility to connect over GMS to synchronize message brokers."
"Best feature is Insight for monitoring, and as a debugging tool. It has saved us a lot of time during crisis situations."
"It integrates well with various servers."
"One [of the most valuable features] is the webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."
"EDI is robust and integration with SAP is good."
"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."
"Operationally, I consider the solution to be quite good."
"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."
 

Cons

"The deployment could be simplified."
"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."
"BizTalk Server is an outdated legacy system that does not support messaging."
"The product could be improved in monitoring, managing, and support functionalities."
"It's an on-premises system, requiring physical servers for deployment. This is different from Azure; you don't need any servers with Azure. If you have a subscription, you can do whatever you want. There are unit restrictions based on the environment (like non-production vs. production) in BizTalk. You need physical servers and databases. In Azure, those are not required – it's all in the cloud."
"Updating things in BizTalk is a headache."
"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."
"The product's deployment can be quicker"
"webMethods.io Integration's installation is complex. It should also improve integration and connectors."
"I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier."
"The product's stability is an area of concern where improvements are required."
"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."
"The solution has big instances when deployed under microservices or in a containerized platform. They need to improve that so that it is competitive with other integration solutions, like Redis and Kafka. Deployments under microservices with those solutions are much more lightweight, in the size of the runtime itself, compared with Software AG."
"The logging capability has room for improvement. That way, we could keep a history of all the transactions. It would be helpful to be able to get to that without having to build a standalone solution to do so."
"The licensing cost is high compared to other options."
"The solution should include REST API calls."
 

Pricing and Cost Advice

"The cost will depend on the client's requirements."
"BizTalk Server is not freeware. There's a significant licensing cost involved. Be sure you will actually utilize its features fully."
"Based on the knowledge, it is relatively cheaper than Azure Identity Services and cloud services in general."
"BizTalk Server is cheap. I would rate its pricing a two out of five."
"The solution is expensive."
"It was not cheap, but it was affordable."
"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."
"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."
"The price is a little bit high, especially regarding their support."
"Initialy good pricing and good, if it comes to Enterprise license agreements."
"The solution's development license is free for three to six months. We have to pay for other things."
"There is a license needed to use the webMethods Integration Server."
"It's a good deal for the money that we pay."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
report
Use our free recommendation engine to learn which Business-to-Business Middleware solutions are best for your needs.
842,651 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Manufacturing Company
12%
Computer Software Company
11%
Retailer
6%
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
13%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about BizTalk Server?
The tool's most valuable feature is its integration with the banks. Its messaging and routing capabilities are good.
What needs improvement with BizTalk Server?
BizTalk is deployed on-premise. Deployment methodologies are vast in the cloud area. Whereas, if we want to update even a single thing on BizTalk, we need to take the DLL, put it in the system, and...
What advice do you have for others considering BizTalk Server?
When I started my career with BizTalk, people told me the vendor would sunset BizTalk Server, but it didn't happen. Higher versions are still being released. The product will not face the sunset. A...
What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
 

Also Known As

No data available
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Centrebet, Seoul National University Bundang Hospital, QualCare, Wªrth Handelsges.m.b.H, DTEK, Allscripts, United BioSource, Hogg Robinson
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about BizTalk Server vs. webMethods.io and other solutions. Updated: March 2025.
842,651 professionals have used our research since 2012.