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

Microsoft System Center Orchestrator 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

Microsoft System Center Orc...
Ranking in Process Automation
19th
Average Rating
7.6
Reviews Sentiment
6.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
Temporal
Ranking in Process Automation
7th
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Dan Campeanu - PeerSpot reviewer
Automates tasks and manages multiple servers from a central location
The initial setup was quite complex. It required careful preparation of installation steps, as many tasks were not automated as expected. Special attention was needed to prepare groups, users, and permissions at each step to ensure a smooth setup process. Please do so accurately to avoid having to start over. Challenges encountered during deployment included issues with installation and configuration and difficulties detecting machines and executing tasks as expected. Some solutions were found through trial and error during installation, while others were discovered through recommendations from other users. Despite these challenges, the deployment and rollout of Orchestrator took approximately one and a half months to ensure proper functionality.
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

"It can manage multiple servers and workstations from a single location."
"Automation is the most valuable feature of the solution."
"Temporal focus on developers rather than business users."
"What I like best about Temporal is its durable execution, which means you don't need to write many boilerplate code for critical pieces, especially for retries. It also has great observability and a nice dashboard to see issues without digging into logs. The interface for viewing activities is excellent, with good tracing that shows how long activities took and what ran, making it almost perfect for debugging."
"We like the fact that the whole process is durable, which is very useful to us."
"It's easy to get started and user-friendly."
"Temporal allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."
"The most valuable feature is its ability to manage and automate workflows without manual intervention efficiently."
"It is very useful for long-running workflows."
"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."
 

Cons

"The product's management aspect needs enhancement."
"I find the Orchestrator UI to be problematic."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
"We previously faced issues with the solution's patch system."
"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 where I think Temporal could improve is its dashboard, particularly in event tracking. Currently, the dashboard doesn't show a time-based view of events, meaning it doesn't display when an event started or went through the retry process. If this feature could be added in a future release, it would significantly enhance monitoring capabilities. Other than that, Temporal's overall performance is quite impressive, and we're confident we can migrate to the Temporal workflow."
"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."
"Temporal's debugging is a bit complex."
 

Pricing and Cost Advice

"I give the cost of the solution a five out of ten."
"We obtained a license that bundled Windows Server with System Center at no additional cost."
"Temporal is a free, open-source tool."
"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 open-source and free to use, which is great. We didn't have to pay for any premium features."
"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."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
846,617 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Government
10%
Manufacturing Company
8%
Computer Software Company
8%
Financial Services Firm
27%
Computer Software Company
18%
Retailer
9%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Microsoft System Center Orchestrator?
It can manage multiple servers and workstations from a single location.
What is your experience regarding pricing and costs for Microsoft System Center Orchestrator?
The platform was almost free of cost for us. We obtained a license that bundled Windows Server with System Center at no additional cost.
What needs improvement with Microsoft System Center Orchestrator?
The product's management aspect needs enhancement. It affects the visibility of powerful scripts that were previously accessible. Furthermore, the focus is shifting towards cloud-based features, sp...
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...
 

Also Known As

MS System Center Orchestrator
No data available
 

Overview

Find out what your peers are saying about Microsoft System Center Orchestrator vs. Temporal and other solutions. Updated: April 2025.
846,617 professionals have used our research since 2012.