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

ServiceNow Orchestration vs Temporal comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

ServiceNow Orchestration
Ranking in Process Automation
12th
Average Rating
8.2
Reviews Sentiment
6.0
Number of Reviews
14
Ranking in other categories
No ranking in other categories
Temporal
Ranking in Process Automation
8th
Average Rating
8.6
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Featured Reviews

ShaheenKapery - PeerSpot reviewer
Easy to integrate, stable solution and incredibly good customer service
It is a long setup. It was customized to our company's requirements. Bearing in mind that there is not just an IT team. You've got an IT team consisting of end-users, consulting, and user support sides. Install support, ServiceNow support, application support, and so on. What ServiceNow does is it's really good at getting the tickets to the right person. That's the power of it. There's no issue with it. But you need to set that up in advance. You need to know the structure and who is responsible for each task. The initial setup does take a long time, and the organization might face some issues. But once you've got that resolved, it's amazing.
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

"This is a user-friendly solution where scripts can be made with ease. There are also many integration options, including Microsoft products, which gives the product a competitive edge."
"The iTerm suite is also crucial for visibility and optimization."
"Employee onboarding, de-boarding, and other service-provision features make the process easier and it saves us a lot of time."
"It's probably the best product out there."
"The product has a flexible interface for development."
"The data visualization is good."
"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 languages like Java. But along with that, there are limitation in terms of network connectivity testing and administrator faces regular challenges in conducting connectivity tests due to these limitations."
"It's scalable."
"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"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."
"The initial setup is easy."
"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 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."
 

Cons

"The flow rate for releases and updates is very, very slow and does not meet customers' objectives for scalability."
"There is still room for more integrations. Or, it would be nice to bundle multiple products together rather than selling everything as a model as that turns out to be a bit costly."
"The automatic remediation needs enhancement, particularly integrating ServiceNow with tools like SolarWinds and Logic Monitor. It is functional, but it needs improvement."
"The deployment requires awareness among the project staff."
"From my space, the only thing that I can say is the spinning up with Google Cloud Services."
"There can be gaps in integration."
"It is a highly complex platform to work on."
"I would like a user experience module to be added."
"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."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"Temporal could be improved by making it more user-friendly for beginners and non-technical staff, ensuring easier integration and usability across different use cases."
"There are areas where Temporal could improve. For instance, calling multiple microservices with Temporal introduces latency due to workflow registration and analytics overhead."
"One issue is that we don't have enough resources in the community to get answers when we face problems. We once had a cross-cluster persistence issue, which we solved using different keys. I think Temporal is good right now, but I'm part of the community and will let you know if I think of any improvements."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
"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."
 

Pricing and Cost Advice

"In terms of price, this solution is at the higher end of what you'll find."
"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."
"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."
"It is not very expensive."
"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."
"The solution is costly and orchestrations are very expensive."
"Pricing is custom to every customer."
"The savings weren't as big as we initially expected, but they were pretty great from a developer's perspective."
"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."
"Temporal is a free, open-source tool."
"It is worth the price."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
816,562 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
14%
Manufacturing Company
8%
Government
7%
Financial Services Firm
28%
Computer Software Company
19%
Retailer
10%
Manufacturing Company
6%
 

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?
There is a lot of complexity in the platform, but that comes with the scalability. It is a highly complex platform to work on. There are changes in their workflow technology, and the flow technolog...
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: October 2024.
816,562 professionals have used our research since 2012.