Thanks for reply @hferentschik
So what you are saying is active-passive deployment. If i am not wrong. But i don’t see documentation around it how to achieve it.
May be what you are saying in one cluster i have everything setup which will process all request. And other cluster will be passive not doing anything, and it will have db which we can replication by some db tool. And when the active node goes down we can bring passive cluster up by some script or manual process.
i was also reading some post, are this post still send true.
And i am also reading active-active deployment is still experimental, is this is still true?
As i see here it says it is experimental, this whole doc is experimental. Self-hosted Multi-Cluster Replication | Temporal Platform Documentation .
I see you mentioning (Temporal components are basically satteless).
But i see @maxim mentioned. The history nodes are stateful. So each workflow id maps to a specific node. So there is no way to prefer closer nodes without a complete architecture redesign.
In this blog Running temporal across multiple Kubernetes clusters - #7 by bascht , second last comment.