Microsoft System Center Orchestrator vs Temporal comparison

Microsoft System Center Orchestrator vs. Temporal

Download the complete report

Helped 850,028 peers since 2012

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

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

Ranking in other categories

No ranking in other categories

Featured Reviews

Dan Campeanu

Security Engineer at ProVision

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.

Read full review

AbhishekDash

Senior Software Engineer at A.P. Moller - Maersk

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.

Read full review

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 allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."

"Temporal provides visibility into workflow progress and analytics and supports scheduled tasks with customizable settings, making it very convenient."

"Temporal focus on developers rather than business users."

"The initial setup is easy."

"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."

"What I like best about the tool is that it's easy to install, especially since it uses JavaScript. It's also easy to set up with Docker, and the documentation is easy to understand."

"We like the fact that the whole process is durable, which is very useful to us."

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

More Temporal pros

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

"Sometimes it scales kind of badly, but it depends on the process of our products."

"We previously faced issues with the solution's patch system."

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

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

"There are areas where Temporal could improve. For instance, calling multiple microservices with Temporal introduces latency due to workflow registration and analytics overhead."

"Developers often mention the desire for a more intuitive visualization of workflow states."

More Temporal cons

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

"The savings weren't as big as we initially expected, but they were pretty great from a developer's perspective."

"Temporal is a free, open-source tool."

"It is worth the price."

See which vendors are best for you

Use our free recommendation engine to learn which Process Automation solutions are best for your needs.

See recommendations

850,028 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

14%

Government

11%

Computer Software Company

Manufacturing Company

Financial Services Firm

27%

Computer Software Company

18%

Retailer

Manufacturing Company

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

ServiceNow Orchestration vs Microsoft System Center Orchestrator

Comparisons

Compared 28% of the time

Camunda vs Microsoft System Center Orchestrator

Compared 23% of the time

BizTalk Server vs Microsoft System Center Orchestrator

Compared 19% of the time

vCenter Orchestrator vs Microsoft System Center Orchestrator

Compared 17% of the time

Rundeck vs Microsoft System Center Orchestrator

Compared 13% of the time

More Microsoft System Center Orchestrator Competitors

Camunda vs Temporal

Compared 49% of the time

Flowable vs Temporal

Compared 16% of the time

Orkes vs Temporal

Compared 14% of the time

Pega Platform vs Temporal

Compared 5% of the time

Rundeck vs Temporal

Compared 4% of the time

More Temporal Competitors

Product Reports

Process Automation

Download Microsoft System Center Orchestrator product report

Microsoft System Center Orchestrator report

Temporal

Download Temporal product report

Also Known As

MS System Center Orchestrator

No data available

Overview

As an IT administrator, you probably perform a lot of tasks and procedures to keep your computing environment healthy. You may have automated individual tasks, but typically, not the whole process. With System Center - Orchestrator you tie disparate tasks and procedures together using a graphical user interface Runbook Designer to create reliable, flexible, and efficient end-to-end solutions in your IT environment.

Microsoft

Temporal automates and manages workflows efficiently, offering resilience in distributed systems with features like retry and fault tolerance. Its capabilities in handling complex workflows and integrating with programming languages make it a valuable tool for managing diverse business logic.

Temporal excels in workflow orchestration, automating tasks across multiple platforms, and ensuring durability in asynchronous operations. It supports long-running workflows and simplifies handling distributed transactions, reducing boilerplate code. Temporal is noted for its durable execution and built-in retry policies, enhancing resilience. Despite its complexity and steep learning curve, it is valued for its integration with popular programming languages and relatively easy setup process, though it requires improvements in user-friendly features, documentation, community support, and security.

What are Temporal's key features?

Automation and Efficient Management: Automatically handles workflows without manual intervention.
Resilience and Fault Tolerance: Features built-in retry policies for increased reliability.
Integration: Supports various programming languages, easing development.
Distributed Transactions: Simplifies complex transaction handling with reduced boilerplate code.
Durable Execution: Ensures long-running workflows are reliably managed.

What benefits or ROI should users evaluate?

Scalability and Reliability: Enhances IT environments through robust workflow management.
Ease of Integration: Supports seamless multi-platform automation.
Improved Operational Efficiency: Reduces need for extensive coding, streamlining processes.
Durability and Fault Tolerance: Provides reliable asynchronous operations.

Temporal is implemented in sectors requiring robust workflow orchestration, such as managing data pipelines, API integration, and scheduling tasks. Organizations in a Kubernetes environment leverage it for its scalability and infrastructure management capabilities, securing integrations and enhancing reliability across IT operations.

Temporal Technologies

Microsoft System Center Orchestrator vs. Temporal