21–30 of 56 posts
Is this equal to Azure Durable Functions?
(disclaimer, I'm the author of the post)
Is this equal to Azure Durable Functions?
Not necessarily "equal" but the basic premise is the same, yes, and there is a common lineage. Azure Durable Functions sits on Azure Durable Task Framework which was created by the co-founder of Temporal ( https://temporal.io/about ). (disclaimer, I'm the author of the post)
Earlier quoted context omitted.
Not necessarily "equal" but the basic premise is the same, yes, and there is a common lineage. Azure Durable Functions sits on Azure Durable Task Framework which was created by the co-founder of Temporal ( https://temporal.io/about ). (disclaimer, I'm the author of the post)
Ohh, that's great to hear! I do like ADF, but the Python worker is full of bugs and weird behaviour and tickets stay open for month without progress. I will definitely check that out!
Excited to get to use it at some point.
For example, in "Implementing a Workflow" the execute_activity refers to Purchaser.purchase, which is not declared anywhere.
If the execute_activity times-out after 1 minutes, the status does not seem to be updated anywhere.
In "Running a Worker", do_purchaser is passed as an activity, without explanation. (I guess I'd need to read the fundamental Temporal docs?)
Read the example code, have a sinking feeling that is not taken from a real tested example. Either there are multiple unexplained symbols or teh code does not actually run. For example, in "Implementing a Workflow" the execute_activity refers to Purchaser.purchase, which is not declared anywhere. If the execute_activity times-out after 1 minutes, the status does not seem to be updated anywhere. In "Running a Worker",…
This is more of a primer on the Python part of Temporal rather than an explanation of all Temporal concepts in depth. Definitely would recommend reading the fundamental docs at https://docs.temporal.io/encyclopedia/. For more exact samples, see https://github.com/temporalio/samples-python.
I can’t understand what layer provides the state orchestration. Like, in celery is redis. What about here?
Anyone migrated from celery, with / without regrets?
Many Temporal users used Celery in the past. There was a popular blog post a while back about issues with celery: https://steve.dignam.xyz/2023/05/20/many-problems-with-celer... . Here's a brief heading-by-heading listing of how Temporal addresses those issues: https://community.temporal.io/t/suggestion-for-blog-post-abo... . (disclaimer, I'm the author of the post)
add.delay(1, 2)
It's relatively small compared to the other issues but it sticks out because it's one of only two listed as "you'll have to live with it".
Earlier quoted context omitted.
Many Temporal users used Celery in the past. There was a popular blog post a while back about issues with celery: https://steve.dignam.xyz/2023/05/20/many-problems-with-celer... . Here's a brief heading-by-heading listing of how Temporal addresses those issues: https://community.temporal.io/t/suggestion-for-blog-post-abo... . (disclaimer, I'm the author of the post)
The "API isn’t Pythonic" examples are misleading, the first and third are using more verbose forms of: add.delay(1, 2) The verbose forms are for when you want extra functionality like in the second example. It's relatively small compared to the other issues but it sticks out because it's one of only two listed as "you'll have to live with it".
I can’t understand what layer provides the state orchestration. Like, in celery is redis. What about here?
The Temporal server stores events and distributes tasks. There is a cloud offering or it can be self-hosted (with support for Cassandra, Postgres, MySQL, and SQLite persistence). This post focuses more on the Temporal Python SDK and not the general platform.