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

ServiceNow Orchestration 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

ServiceNow Orchestration
Ranking in Process Automation
11th
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
15
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

Dinesh Kumar Raghu - PeerSpot reviewer
Fastest upgrading technology in the market currently
In each upgrade, ServiceNow is enhancing its product across various areas. They continuously improve different aspects one by one, ensuring that their service evolves with the changing needs. However, frequent upgrades may negatively impact the performance of instances. Therefore, for now, I don't recommend any additional upgrades. The current version fulfills everyone's requirements, and ServiceNow automatically updates annually, keeping pace with industry standards. They've been performing well, so I see no need for further upgrades, especially considering their consistent updates.
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 is a very stable product, highly affordable."
"The data visualization is good."
"Employee onboarding, de-boarding, and other service-provision features make the process easier and it saves us a lot of time."
"It has competitive AI capabilities."
"It's scalable."
"Orchestration is commonly utilized by major corporations. The process of linking methods in ServiceNow, known as the RTS chain to parent methods, is executed seamlessly and efficiently. It's quite impressive and significant in its impact."
"The solution effectively automates business processes."
"There are a lot of ready to use orchestration custom packs."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"Temporal allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."
"The solution's most valuable feature is its ability to fix things quickly."
"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."
"The initial setup is easy."
"Temporal focus on developers rather than business users."
"The most valuable feature is its ability to manage and automate workflows without manual intervention efficiently."
"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."
 

Cons

"ServiceNow Orchestration needs to improve multiple aspects in which their event monitoring system is one. The solution lacks event monitoring systems which makes them non-competitive. They need to include improvements in a similar manner that they did in Sweden."
"It is a highly complex platform to work on."
"We cannot perform GUI automation using the tool."
"Frequent upgrades may negatively impact the performance of instances. Therefore, for now, I don't recommend any additional upgrades."
"The flow rate for releases and updates is very, very slow and does not meet customers' objectives for scalability."
"There can be gaps in integration."
"Efficiency of some features could be improved."
"The deployment requires awareness among the project staff."
"Temporal lacks many resources, like YouTube videos, which users can use to learn or refer to if they get stuck with the solution."
"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 images aren’t FIPS compliant, and we have to be FIPS compliant."
"Sometimes it scales kind of badly, but it depends on the process of our products."
"Temporal's debugging is a bit complex."
"Configuring workflows can be improved —the solution could offer more options, but it's not a must-have."
"Developers often mention the desire for a more intuitive visualization of workflow states."
"One area for the product improvement is the learning curve."
 

Pricing and Cost Advice

"The solution is costly and orchestrations are very expensive."
"The cost of the solution is based on the number of plugins, conductors and integrations used and is charged annually. The licensing cause has been increasing gradually which makes it difficult to access. Initially offer free features but over the time the charges rise which make it an expensive solution with limited features. Along with that, the integration issues persist and require additional middle where and internet connectivity for effective usage."
"This is an expensive product, but it is the best in the market considering the features and lack of competitors."
"It is quite expensive because we've had some customers come back and say it's quite pricey because in order for them to go ahead with Orchestration, they must have already been paying for Discovery, service mapping, and a few other things."
"In terms of price, this solution is at the higher end of what you'll find."
"ServiceNow doesn't give a clear cost indication. They have different contracts with different organizations and it's all about negotiation, so you don't know how they are doing at the cost level."
"Pricing is custom to every customer."
"It is not very expensive."
"It is worth the price."
"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."
"Temporal is open-source and free to use, which is great. We didn't have to pay for any premium features."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
831,997 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Computer Software Company
13%
Manufacturing Company
8%
Insurance Company
7%
Financial Services Firm
30%
Computer Software Company
16%
Retailer
13%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about ServiceNow Orchestration?
The interface of the solution is very user friendly and it is easily accessible via a simple URL. This makes it easier to complete the UI based tasks but using other features require expertise in l...
What needs improvement with ServiceNow Orchestration?
I remember last time I said there is no need for improvement. It's fine. Due to the limited scope, I cannot comment further. However, it should be integrated with AI and messaging or chatting featu...
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...
 

Overview

 

Sample Customers

experian, BEACHBODY, HealthPartners, Banosoft
Information Not Available
Find out what your peers are saying about ServiceNow Orchestration vs. Temporal and other solutions. Updated: January 2025.
831,997 professionals have used our research since 2012.