bergundy
Re:Red Engine: modern scheduling framework for Python applications
on Sunday July 03, 2022 @05:31PM (#31971209)
Going to shamelessly plug Temporal’s Python SDK which was designed for asyncio.
https://github.com/temporalio/sdk-python
Disclaimer: I work for Temporal
Re:Temporal raises $103M in Series B funding
on Wednesday February 16, 2022 @07:57PM (#30368221)
Yes, that's what I meant, I should have made that clearer
Re:Temporal raises $103M in Series B funding
on Wednesday February 16, 2022 @06:26PM (#30367284)
I like to think about it in terms of what the code for managing a shopping looks like.
Without Temporal, you store the state of the cart in the DB, load it when the app interacts with your backend, run some business logic and serialize state back into the DB.
With Temporal, first of all, there's no DB. The entire flow is modeled in a single piece of code. Your Workflow can listen to user signals to update the cart, queries to get the cart state, schedule durable timers to remind a user that their cart is abandoned after days and months.
Re:Queue Despair: Ordering and Poison Messages
on Wednesday December 08, 2021 @04:18PM (#29490648)
Instead of directly using queues in a Temporal Workflow, the Workflow (which is written with plain code), schedules an Activity that the system is responsible for, behind the scenes, the Activity is just an item put on a queue.
Activities have retry policies which are also handled by the system.
If an Activity attempt fails and should not retry according to the policy, an exception is thrown in the Workflow to be handled using code.
Using the TypeScript SDK, you can catch that exception here: https://github.com/temporalio/samples-typescript/blob/9d9108...