I highly recommend Temporal for building critical systems that involve distributed transactions. It's an excellent choice for such scenarios. The cloud option is a good fit if you want to minimize CapEx and don't have many long-running workloads or operations running continuously. Building and managing it in-house might be more cost-effective if you have substantial use cases with many teams or numerous workloads that need to run persistently. Overall, I rate the solution an eight-point five out of ten.
The project I was working on was an AI project. We used to bring data from different sources using Temporal and put it into Elasticsearch. We would then take data from Elasticsearch, implement some AI logic on it, and insert it back into Elasticsearch. AI logic was implemented in Python codes, and our Temporal job was to do the calculations using Python codes and dump the data back into Elasticsearch. I suggest not using Temporal if your product is vital because if you are stuck somewhere, you will hardly get any resources. You will have to spend a lot of time to find out some functionality. Temporal has very limited documentation. If we have some POCs that are not so vital, then we can use Temporal to check something. I was able to do some basic things. However, you will find very little documentation or examples if you want to implement some big things. You must spend a lot of time understanding the functionality or connecting with the Temporal team to understand it. It is easy for a beginner to learn to use the solution for the first time. A new user may take around 15 days to one month to understand workflows. I also took around one month to understand the tool and then try to implement it. Overall, I rate the solution a seven out of ten.
Temporal delivers durable execution. It abstracts away the complexity of building scalable distributed systems and lets you keep focus on what matters – delivering reliable systems, faster. It allows you to avoid coding for infrastructure nuances and their inevitable failures.
Temporal eliminates recovery logic, callbacks, and timers from your code so you can spend more time building features.
Temporal makes your software durable and fault tolerant by default, reducing failures by 10-100X....
I highly recommend Temporal for building critical systems that involve distributed transactions. It's an excellent choice for such scenarios. The cloud option is a good fit if you want to minimize CapEx and don't have many long-running workloads or operations running continuously. Building and managing it in-house might be more cost-effective if you have substantial use cases with many teams or numerous workloads that need to run persistently. Overall, I rate the solution an eight-point five out of ten.
The project I was working on was an AI project. We used to bring data from different sources using Temporal and put it into Elasticsearch. We would then take data from Elasticsearch, implement some AI logic on it, and insert it back into Elasticsearch. AI logic was implemented in Python codes, and our Temporal job was to do the calculations using Python codes and dump the data back into Elasticsearch. I suggest not using Temporal if your product is vital because if you are stuck somewhere, you will hardly get any resources. You will have to spend a lot of time to find out some functionality. Temporal has very limited documentation. If we have some POCs that are not so vital, then we can use Temporal to check something. I was able to do some basic things. However, you will find very little documentation or examples if you want to implement some big things. You must spend a lot of time understanding the functionality or connecting with the Temporal team to understand it. It is easy for a beginner to learn to use the solution for the first time. A new user may take around 15 days to one month to understand workflows. I also took around one month to understand the tool and then try to implement it. Overall, I rate the solution a seven out of ten.