Temporal Reviews

We use this solution to power an internal workflow engine we've developed. Currently, it's being used within our company to manage workloads running on the orchestration platform.

Temporal fault tolerance has been beneficial for our critical business operations. It handles scheduled tasks and failures effectively, automatically retrying processes in case of issues. Additionally, our workflows are managed smoothly, with our internal engine providing inputs toTemporal for task execution. As for AI-driven projects, we haven't utilized Temporal in this domain yet.

The most valuable feature is its ability to manage and automate workflows without manual intervention efficiently. This includes handling functions and activities and orchestrating various tasks seamlessly. Temporal's reliability and performance have been exceptional for us, even with thousands of workflows running daily on-premises.

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.

I have been using Temporal for the past year and a half.

In my experience, I haven't encountered any issues or bugs. Everything has been working smoothly.

It is very scalable. We can run thousands of workflows simultaneously without any issues, so scalability-wise, it's perfect.

The initial setup of Temporal is straightforward. It's similar to deploying other servers; you must adjust the resources if necessary. Overall, no special knowledge is required.

I would rate it an eight because while it's robust and scalable, once you're familiar with it, there's a learning curve for newcomers due to the complexities involved. Additionally, managing specific errors and concepts can be initially challenging. However, its scalability and open-source nature are significant advantages.

We needed to implement different workflows for various processes, each involving distinct steps. We used these workflows to handle large data flows or complex operations within our system. We employed them to limit rates, as it was the simplest solution. Furthermore, we implemented some cron jobs, not because they were required but because we wanted to avoid excessive zooming.

It is fairly easy, though it has some undefined aspects if you're unfamiliar with it. For instance, you need to properly define your functions and handle various small issues that can arise. It's easy to get started and user-friendly. There are some internal challenges. For example, I initially missed some error handling and connectivity issues, which led to problems because I implemented things incorrectly. 

I don't like the limitations on data flow, particularly the difficulty of passing large amounts of data between different activities. I encountered issues with this and explored various approaches. I decided to store the data in files, but there were other methods. This was redundant because it added complexity to the implementation, making it more challenging to manage.

I have been using Temporal for about a year.

Due to an overload on our cluster, we encountered some problems. We started too many tasks simultaneously. Initially, we attempted to run many tasks at once, but this approach caused issues.

I rate the solution’s stability a five out of ten.

The system has good scalability, though it does have some limitations. For instance, Postgres handles scalability well up to a certain point, typically around eight to ten instances. Using a NoSQL database might address some scaling issues more effectively. Postgres was sufficient, and we could work within its constraints.

I rate the solution’s scalability an eight out of ten.

You can use it for free if you want.

In most cases, you don't need extensive prior knowledge to use this technology; the documentation is usually sufficient. It was likely my mistake for not understanding the problem correctly, even though it was logically straightforward. Fortunately, we had an experienced developer on our team who helped me identify some best practices.

I recommend this technology even to large tech companies. It’s pretty substantial and impactful. I suggest reading the documentation more carefully, as it affected my experience.

Overall, I rate the solution an eight out of ten.