8 entries
Temporal provides helpful primitives called Workflows and Activities for orchestrating processes. A common pattern I've found useful is the ability to run multiple "child workflows" in parallel from a single "parent" workflow.
I played around with trying to run a Temporal worker on Modal. I didn't do a ton of research upfront -- I just kind of gave it a shot. I suspect this isn't possible. Both use Python magic to do the things they do. This is what I tried.
Temporal gives you flexibility to define different task queues to route workflows and activities to specific workers. When a worker starts up, it is configured to consume from a specific task queue by name, along with the activities and workflows it is capable of running.
Setup a Temporal worker in Ruby and got familiar with its ergonomics.
I started to play around a bit with trying to setup a Temporal worker using Deno, but quickly ran into issues, then learned this isn't currently possible.
It's much easier to test Temporal Workflow in Python by invoking the contents of the individual Activities first, in the shell or via a separate script, then composing them into a Workflow. I need to see if there's a better way to surface exceptions and failures through Temporal directly to make...
A spot where I slipped up in trying to adopt Temporal in an existing Python project and then again in starting a new Python project was in defining a Workflow that invokes an Activity that calls a third party library. Temporal outputs an error message with a long stacktrace that I vaguely...
I've been doing a bit of work with Temporal using it's Python SDK. Temporal remains one of my favorite pieces of technology to work with. The team is very thoughtful with their API design and it provides a clean abstraction for building distributed, resilient workflows. It's a piece of technology...