We use Temporal in our company to create child components and complete workflows that are dependent on each other. We also use it for child workflows and employee task orientation.
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.


| Author info | Rating | Review Summary |
|---|---|---|
| Sde Ii at Greytip Software Pvt. Ltd. | 4.5 | I use Temporal for complex, scalable workflows, integrating with AWS for high-load form processing. While stable, I find community support lacking and desire longer cloud certificate expiry and default workflow expiration to prevent server overload. |

We use Temporal in our company to create child components and complete workflows that are dependent on each other. We also use it for child workflows and employee task orientation.
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.
We convert RSA files to PKCS format for integration and have configuration settings. Many libraries help integrate the tool, making it easy to implement in Java and Python.
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.
We use the cloud version of Temporal. They provide a key that we insert in our files to execute functionality. Our certificate expires in one year, which can cause issues in the product. It would be beneficial if the certificate expiry timeline could be extended to two or three years, as changing it every year is challenging.
One issue is that workflows without an expiry time can run indefinitely, overloading the server. It would be helpful to have a default timeline that automatically deletes or removes workflows after a month.
I have been working with the product for a year.
The tool doesn't have any performance issues.
The solution's scalability is high.
I haven't contacted support yet.
Before Temporal, we tried to implement Kafka, but Temporal was better suited to our use cases. We evaluated Kafka but decided to go with Temporal.
The initial setup can be tough for beginners as it's not like simple coding languages. You must understand how functions work, including small things like run methods. I followed the personal document. Three to four people were involved in the deployment. Deployment locally can take one or two days, including all activity checks and finalizing components.
I rate the overall solution a nine out of ten.
| Product | Mindshare (%) |
|---|---|
| Temporal | 3.3% |
| Camunda | 10.0% |
| IBM BPM | 5.8% |
| Other | 80.9% |
| Company Size | Count |
|---|---|
| Small Business | 7 |
| Midsize Enterprise | 4 |
| Large Enterprise | 6 |
| Company Size | Count |
|---|---|
| Small Business | 150 |
| Midsize Enterprise | 85 |
| Large Enterprise | 351 |
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?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.