1 year ago

#370440

test-img

prashant

Temporal workflow hardware constraints for low latency

I have recently started reading about temporal for use in my company's project. I have built an in-house orchestrator for short lived tasks which is able to support 100 tps with 8 gb heap and 4 cores. I am running on a oracle database with 16gb and 4 cores.

My in-house orchestrator uses kafka as an event source and a trie to model a DSL using which the next service to be invoked is decided. On comparing my simple orchestrator with temporal I see that while temporal has more features for resiliency and instrumentation of workflows it seems to be taking too much hardware and does not seem to have a focus on low latency. Is my observation correct and should I look for a combination of my low latency orchestrator with temporal or am I missing something here.

low-latency

temporal-workflow

0 Answers

Your Answer

Accepted video resources