Hello, I have some question about how to setup my ...
# support-questions-legacy
d
Hello, I have some question about how to setup my multi-server architecture with supertokens. My goal is to have at least one server for each country we are deploying our device (because it will host some medical data), and perhpas several, for United States (in the future). My question is: is there a way to deploy my self-hosted supertokens on several servers and sync all of them together ? Or there's not pre-built solution for this situation ?
r
hey @DollarNavalex when you say sync all the core, what do you mean? Do you want to have one user pool across all your regions, or would they be isolated user pools, one per region? Do you need to have data isolation and data processing isolation (per region)? Or just data isolation?
d
Well the goal would be to have one user pool global across all my regions. What do you mean by data isolation ? Because all the sensitive medical data will be managed by my backend, so it should not pass through supertokens core. Except if the supertokens backend sdk process all request payloads ?
r
i mean, for each region, do you want to store that region's data in a database isolated to that region?
d
To be honest, i don’t really know but I would say no for the moment
If I can have one core with one database and one user pool at the same place and available all around the world it should do the job
r
yea, you can do that. Host the core in any one region and store all the data there
performance wont be affected too much cause most requests won't go to the core anyway.
d
Hm, i thought all request protected by a session would talk to the core to check session integrity
The sdk do most of the job then ?
r
yes. The sessino verification is stateless, so no need to contact the core
d
Okay that’s huge ! So the back talk to the core only during sign in/up and related requests ?
r
yes, and also during session refresh, but that happens relatively rarely anyway
d
Okay, well thanks that clarify a lot 🙂