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

Oracle BPEL 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

Oracle BPEL
Ranking in Process Automation
25th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
4
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

PN
A highly scalable solution that provides various features for the execution of business processes
I'm a consultant. I do architecting, designing, and development. I have used two versions, 1.1 and 2.0. I’m unsure about the prices because I oversee the development and implementation. I'll highly recommend the product depending on an organization’s requirements. As someone who has worked with BPEL for 13 years, I highly recommend the product for an on-premise or hybrid integration. Multiple products or alternate solutions have come into the integration domain. However, the product has been in the industry from SOA 11g to SOA 12c and OIC. Though there are multiple competitors, the product has been here for a long time and has been helping multiple customers improve their business. Overall, I rate the solution a nine or nine and a half out of ten.
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

"What I find the most valuable about Oracle BPEL is that it saves me time."
"The product has everything we need."
"The solution is very seamless and fast."
"The most valuable feature is the support for human tasks."
"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."
"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 solution's most valuable feature is its ability to fix things quickly."
"The most valuable thing about Temporal is that we can create multiple and child workflows. We can segregate work as we want, which is good for work organization. It's also easy to maintain. We're trying to generate and fill PDF forms with custom data, including digital signatures. We call AWS and do all activities through Temporal, like calling and saving data in buckets. We do this because we have a lot of load, with multiple users requesting data. We have two types of users: admin and customer. The admin creates forms, and employees or customers fill them out. When admin gets a form, it's stored in Temporal."
"Temporal focus on developers rather than business users."
"We like the fact that the whole process is durable, which is very useful to us."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"It's easy to get started and user-friendly."
 

Cons

"They need to have support for new protocols like GraphQL and possibly some out-of-the-box adapters for SAP and other big systems."
"The solution's integration with SAP should be seamless because some formats are not accepted in SAP but are accepted in Oracle BPEL."
"Some user-defined functions for transformation must be added to the next release of the solution."
"In the next release, I would like to see REST improved and new technologies for microservices. I'd like to see more containers for separating containers."
"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."
"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."
"Temporal lacks many resources, like YouTube videos, which users can use to learn or refer to if they get stuck with the solution."
"Temporal's debugging is a bit complex."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"Developers often mention the desire for a more intuitive visualization of workflow states."
 

Pricing and Cost Advice

"The product is moderately priced."
"The solution's pricing is moderate and not expensive."
"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."
"It is worth the price."
"Temporal is a free, open-source tool."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
847,959 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
13%
Financial Services Firm
13%
Computer Software Company
11%
Government
10%
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 needs improvement with Oracle BPEL?
They need to have support for new protocols like GraphQL and possibly some out-of-the-box adapters for SAP and other big systems. It should be better if the SAP adapter were included in the bundle.
What is your primary use case for Oracle BPEL?
We primarily use Oracle BPEL for process automation. It is used for workflows for documents, data transfers, and other processes implemented for our customers.
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...
 

Comparisons

 

Also Known As

BPEL Process Manager
No data available
 

Overview

 

Sample Customers

Nacional Monte de Piedad IAP, Bimbo S.A. de C.V., Intelligent Pathways, DVZ Datenverarbeitungszentrum Mecklenburg-Vorpommern GmbH, Arqiva
Information Not Available
Find out what your peers are saying about Oracle BPEL vs. Temporal and other solutions. Updated: April 2025.
847,959 professionals have used our research since 2012.