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

OpenText Operations 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

OpenText Operations Orchest...
Ranking in Process Automation
22nd
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
26
Ranking in other categories
Robotic Process Automation (RPA) (21st)
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

Ahmed Salman - PeerSpot reviewer
Increases productivity with automation and robust orchestration capabilities
The community is very powerful, with extensive knowledge bases available. There are ready-made workflows, integration with other products, a nice user interface, and reporting. The tool is flexible, agent-based or agentless. It allows significant automation and has robust orchestration and reporting capabilities. It is easy to configure and use, leading to increased efficiency across our IT processes.
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's very stable. If you ask me for the success rate metrics, it's more than 90% for both."
"The product is good functionality-wise. I am impressed with the tool's flexibility in customization."
"It has reduced the time taken to go to market. In the past, we were struggling with building these integrations, but now the process has sped up and there is an added advantage of quick delivery. In addition, it is an agent-less solution, which provides more flexibility in terms of multiple options."
"The community is very powerful, with extensive knowledge bases available."
"In my environment, if I want to shut down all tools in one shot, I can create a workflow and run the workflow to shut down all tools in one go."
"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."
"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."
"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."
"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 solution's most valuable feature is its ability to retry from an interrupted state."
"The solution's most valuable feature is its ability to fix things quickly."
 

Cons

"The price is an area that should be addressed because the price is high."
"The tool's UI needs to be improved. It needs to have better administration features in future releases."
"There were a lot of scalability issues that we initially faced. Whenever I tried to deploy 100-200 endpoints, it became a huge challenge. We had to actually start using other tools like Tivoli Endpoint Management in order to patch the issues."
"I would prefer the addition of ready-made workflows for common scenarios such as Oracle database switchovers or Exchange server scenarios."
"Only the tool's support can be a drawback where improvements are needed."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"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."
"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."
"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 doesn't have built-in data storage to store the state of the ongoing execution."
"I don't like the limitations on data flow, particularly the difficulty of passing large amounts of data between different activities."
"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."
 

Pricing and Cost Advice

"The tool is expensive. I rate the tool a six if one is cheap and ten is very expensive."
"The cost is very high compared to anything else available."
"I do not have experience with the pricing or licensing of the product."
"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."
"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."
"It is worth the price."
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
27%
Computer Software Company
10%
Manufacturing Company
9%
Healthcare 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
 

Questions from the Community

What is your experience regarding pricing and costs for Operations Orchestration?
The pricing is medium, and the automation helps in cost and time savings, resulting in substantial value for money.
What needs improvement with Operations Orchestration?
I would prefer the addition of ready-made workflows for common scenarios such as Oracle database switchovers or Exchange server scenarios. This would save time by not starting from scratch each time.
What advice do you have for others considering Operations Orchestration?
This tool serves as a central management hub, allowing seamless control of various IT processes via one console. I rate this solution eight out of ten.
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

Micro Focus Operations Orchestration, Operations Orchestration, HPOO, HPE Operations Orchestration
No data available
 

Overview

 

Sample Customers

Casablanca INT, Internet Initiative Japan, Railway Information Systems, Samsung SDS, and Turkcell.
Information Not Available
Find out what your peers are saying about OpenText Operations Orchestration vs. Temporal and other solutions. Updated: April 2025.
846,617 professionals have used our research since 2012.