Temporal raises 19M from Sequoia – durable microservices orchestration

Re:Temporal raises 19M from Sequoia – durable microservices ... by andrewingram on Friday October 16, 2020 @08:04AM (#24799943)

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)

[ Parent | on HN ]

Re:Temporal raises 19M from Sequoia – durable microservices ... by geomagilles on Friday October 16, 2020 @09:20AM (#24800525)

Hi 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-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-o...)

[ Parent | on HN ]