@sds
We use Temporal for a subset of high-value jobs (read: money processing), but it felt like overkill for all jobs, especially at the volume we were doing.
If you really care about what the exact state of a job is and it’s not an inherently idempotent operation that can simply be retried, Temporal seems to be a reliable choice.
Haven’t heard of oban—thanks for putting it on the radar. In our case, it’s really nice to have the job framework also written in TypeScript, since our entire backend codebase is TypeScript.
1 reply
0 recast
0 reaction