I noticed airflow as the backing orchestration service. Was there any consideration for another orchestration tool? I know Airbnb has at least two internally, but also that airflow is the predominant one for the data org still.
Milwaukie, Oregon to be exact. It’s a fairly small city just on the edge of south Portland, but it punches above its weight class in terms of successful businesses. Bobs Red Mill, Dark Horse Comics and Dave’s Killer Bread all are headquartered here.
I don’t consider the sleep and auto retry features that interesting, but definitely nice to have.
The advantages to me are the the ability to easily have long-lived “workflows” that are written in the language of your choice (5 SDKs the moment), remove the need for storing state in your application database (even remove the need for a database all together for some services), handle the rough edges around distributed concurrency, and provide out of the box visibility into workflow states.
It does seem like it would be overkill for simple use cases, but with the SaaS offering being so compelling IMHO, I think it can make sense to put smaller use cases there if there is a chance of more use cases in the future.
It does sound like you have more production experience with temporal than me though, so please push back if my glasses are a bit rosey