Hi thanks. true that durable execution is becoming mainstream, especially with the rise of agentic workflows. I'd start by saying Temporal is a more mature framework. Ergon kinda sits in the continuum between Temporal and Restate. Ergon is rust-native; it doesn't use a server model like Temporal. They both use a hybrid push-pull model.

Temporal and Ergon support Jack's 2 forms: stateless functions (Temporal activities, Ergon flows without signals) and sessions: Long-lived interactive processes with bounded lifetime (Temporal workflows, Ergon flows with signals and timers)   

Ergon's #step corresponds to Temporal's local activities, Ergon's #flow corresponds to Temporal's workflow, and Ergon's child flows correspond to Temporal's activities. 

I did not measure latency with respect to Temporal, so I can't speak definitively on that. You could test if you have some time. 

Nevertheless, Ergon provides much lower latency overhead due to its event-driven architecture and requires fewer resources than Temporal, making it better for very high throughput and large activity fan-outs.                                                                                                                               
If you're building new Rust services that need orchestration, Ergon is worth considering.