Try our new research platform with insights from 80,000+ expert users
Software Engineer at a tech vendor with 5,001-10,000 employees
Real User
Top 10
Provide easy to use and documentation to support workflows
Pros and Cons
  • "It's easy to get started and user-friendly."
  • "I don't like the limitations on data flow, particularly the difficulty of passing large amounts of data between different activities."

What is our primary use case?

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.

What is most valuable?

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. 

What needs improvement?

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.

For how long have I used the solution?

I have been using Temporal for about a year.

Buyer's Guide
Temporal
October 2024
Learn what your peers think about Temporal. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,763 professionals have used our research since 2012.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

What's my experience with pricing, setup cost, and licensing?

You can use it for free if you want.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user