4 ms·

Thanks for posting this. I'm curious how this differs from Uber/Cadence, and Temporal (https://www.temporal.io/ https://www.temporal.io/) which is a fork of cad

Thanks for posting this. I'm curious how this differs from Uber/Cadence, and Temporal (https://www.temporal.io/ https://www.temporal.io/) which is a fork of cadence. They're both also distributed workflow scheduling and state management

maxmcd 6y ago
This seems to be more of a distributed cron or general purpose job runner. I believe Temporal/Cadence allow for much more rich composition. Linked actions with Odin seems limited to this mechanism: https://github.com/theycallmemac/odin/blob/master/DOCS.md#link-jobs-together https://github.com/theycallmemac/odin/blob/master/DOCS.md#li...
dnautics 6y ago
I got confused because I'm most faimilar with Oban, which is a distributed workflow manager and scheduler written in a different language: https://github.com/sorentwo/oban https://github.com/sorentwo/oban
ojs 6y ago
So Odin is actually configurable workflows in four supported runtime at the moment - Python, Go, Node and Bash. Temporal seems to only support Java and Go as far as I can see! Specifically, the observability hooks in Odin would be the differentiating feature. Information is gathered to help infer the internal state of jobs. This means Odin can directly help diagnose where the problems are and get to the root cause of any interruptions. Debugging, but you're one step ahead.