This is a "Yes/No" question: Can multiple instances of temporal be backed by the same database?
I want to use a single (HA, geo-redundant) Cloud SQL to store workflow state with multiple (geo-redundant) workers sharing that DB.
I can't find anything in the documentation that answers this question.
Temporal out of the box provides support for multi-node setup. The only requirement is that nodes should be able to talk to each other and the backend database to maintain the cluster membership.
The temporal cluster consists of nodes that play different roles: front-end, history, worker, matching. The roles can be collocated, but it is not recommended for production deployments. Any of the nodes can be added and removed at any time without downtime assuming that enough capacity of each type is maintained to support the application load.