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

BizTalk Server vs Temporal comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

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 Process Automation
14th
Average Rating
7.4
Reviews Sentiment
6.4
Number of Reviews
14
Ranking in other categories
Business-to-Business Middleware (8th)
Temporal
Ranking in Process Automation
3rd
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2025, in the Process Automation category, the mindshare of BizTalk Server is 0.8%, up from 0.7% compared to the previous year. The mindshare of Temporal is 7.0%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation
 

Featured Reviews

Vignesh Kumar Sekar - PeerSpot reviewer
Enables message routing and provides a secure way to communicate between two systems
The AS2 communication protocol is one of the most advanced processes. It enables a handshake with the source and target systems using certificates. It is the most secure way of communicating between two systems. It is an advantage. We can do a lot of message routing. If we want to handle large data, we can put the data into different patterns to process it. We can do it through sequential convoy or parallel convoy orchestration. BizTalk comes with SQL Server. We can load temporary data in the database and use the batch process from BizTalk. It is an added advantage. Creating agreements is a manual job, but it's quite easy in BizTalk. Even a fresh college graduate can configure AS2 certificates and partner profiles and communicate with other systems. It is easy.
AbhishekDash - PeerSpot reviewer
Orchestrates infrastructure tasks like deployment, deletion, and management
Temporal focus on developers rather than business users. In contrast to older workflow orchestration engines like Camunda, which are more business-oriented and strongly emphasize UI and workflow authoring, Temporal is geared toward developers. It provides extensive capabilities for building complex workflows. A standout feature of Temporal is its handling of long-running workflows, a significant advantage over many other solutions. Temporal excels in managing distributed transactions and application state durability, especially in microservice environments where transactions might fail due to network issues. Temporal simplifies these challenges by managing retries, fail-safes, and circuit breakers. As a result, developers don't need to implement these features manually; Temporal handles them implicitly, though it also allows for tuning based on specific needs.

Quotes from Members

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

Pros

"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."
"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."
"I rate the tool's stability a nine out of ten."
"The tool's most valuable feature is its integration with the banks. Its messaging and routing capabilities are good."
"BizTalk Server offers workflow functionality that I find very effective for process automation."
"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 is its ability to manage and automate workflows without manual intervention efficiently."
"The initial setup is easy."
"Temporal provides visibility into workflow progress and analytics and supports scheduled tasks with customizable settings, making it very convenient."
"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."
"The tool is easy for a beginner to learn. The documentation covers activities, workflows, workers, servers, and more. While more examples could be beneficial, the existing resources are good enough to help you get started. There are also YouTube videos available that can provide additional context. The Slack community for Temporal is very active and helpful, similar to Stack Overflow, where you can find answers to a wide range of questions from basic to advanced levels. If you have a unique question, the community is responsive and provides knowledgeable support."
"Temporal allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."
"The solution's most valuable features include its ability to simplify the management of complex workflows, improve system resilience and fault tolerance, and reduce the need for extensive boilerplate code."
"It's easy to get started and user-friendly."
 

Cons

"The product's deployment can be quicker"
"The deployment could be simplified."
"BizTalk Server needs improvements, especially because we use it for EDI messaging, and it would be very useful to have enhanced tracking capabilities for message tracking and archiving of messages."
"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."
"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 is in the past, Microsoft is not going to evolve it any further or add any new features."
"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 could be improved in monitoring, managing, and support functionalities."
"Temporal lacks many resources, like YouTube videos, which users can use to learn or refer to if they get stuck with the solution."
"One area for the product improvement is the learning curve."
"Retro compatibility needs improvement. Sometimes, when we make new changes to a workflow, it fails if it is not configured properly due to compatibility issues."
"While the tool can be a bit daunting initially, especially if you're not used to async programming models, it's generally a pleasure. There's always room for improvement, though. I've noticed some limitations with the .NET SDK regarding dynamic workflows, but this might have been improved in recent versions. Overall, I think Temporal could be more open about implementing features in a more—.NET-friendly way, especially in how you add workers and clients."
"Configuring workflows can be improved —the solution could offer more options, but it's not a must-have."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"There are areas where Temporal could improve. For instance, calling multiple microservices with Temporal introduces latency due to workflow registration and analytics overhead."
 

Pricing and Cost Advice

"The cost will depend on the client's requirements."
"Based on the knowledge, it is relatively cheaper than Azure Identity Services and cloud services in general."
"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."
"The solution is expensive."
"It was not cheap, but it was affordable."
"The tool is open source under the MIT license, so there are no hidden fees. You can freely use everything on their GitHub and Docker images."
"Temporal is open-source and free to use, which is great. We didn't have to pay for any premium features."
"The savings weren't as big as we initially expected, but they were pretty great from a developer's perspective."
"It is worth the price."
"Temporal is a free, open-source tool."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
859,129 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
13%
Computer Software Company
11%
Healthcare Company
7%
Financial Services Firm
28%
Computer Software Company
16%
Retailer
8%
Manufacturing Company
6%
 

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 Server needs improvements, especially because we use it for EDI messaging, and it would be very useful to have enhanced tracking capabilities for message tracking and archiving of messages....
What advice do you have for others considering BizTalk Server?
BizTalk Server has adapted to the changing needs of business over time with steady development, but there are new requirements, for example, on APIs, application programming interfaces. That functi...
What is your experience regarding pricing and costs for Temporal?
Temporal OSS is expensive in infrastructure, but it brings back the reliability that companies need.
What needs improvement with Temporal?
The actual user interface is still in its early stages. It’s very basic. Users don’t really have a complex permission model yet. Users don’t really have ways to automate things like, for example, p...
What is your primary use case for Temporal?
We [my company] use it to run a large workload. We have a set of security scans we want to perform, and we distribute them over a full day, that’s over 24 hours. We use it to orchestrate all the st...
 

Comparisons

 

Overview

 

Sample Customers

Centrebet, Seoul National University Bundang Hospital, QualCare, Wªrth Handelsges.m.b.H, DTEK, Allscripts, United BioSource, Hogg Robinson
Information Not Available
Find out what your peers are saying about BizTalk Server vs. Temporal and other solutions. Updated: June 2025.
859,129 professionals have used our research since 2012.