2 ms·
Please correct me if i'm way off base, but at the mental model level, it seems like the key difference between this and Zenaton is: * Support for multiple lang
by andrewingram 6y ago
Please correct me if i'm way off base, but at the mental model level, it seems like the key difference between this and Zenaton is:
* Support for multiple languages (Zenaton used to, but doubled-down on Node)
* It runs on your own infrastructure (with Zenaton the code runs on your own machines, but the scheduler runs in their systems)
* A deeper focus on resilience (hard to quantify whether Zenaton has this, but it's definitely not emphasised as heavily)
- geomagilles 6y agoHi Andrew, I'm Zenaton's cofounder and you are right Temporal and Zenaton follow the same "workflow as code" pattern. I've written an article recently about it (https://medium.com/swlh/code-is-the-best-dsl-for-building-workflows-548d6824f549?source=friends_link&sk=196dee2ea1f9d5f5b275f0772dfa5d94 https://medium.com/swlh/code-is-the-best-dsl-for-building-wo...) - Note that Zenaton is closed now (not enough commercial traction) and I'm working on a new open-source (well Common clauses) implementation of a workflow-as-code engine - similar to Temporal - but with different technical choices (cf. https://medium.com/@gillesbarbier/building-an-event-driven-orchestration-engine-bf62d45aef5d https://medium.com/@gillesbarbier/building-an-event-driven-o...)