Hey, I have two servers, one in the US and one in ...
# support-questions-legacyt
tuyho
02/04/2023, 12:33 PMHey, I have two servers, one in the US and one in Germany, both running Postgresql 15, the primary being in Germany. I want to store EU customers on my server in Germany, and from North America in the US. Is there a guide for this? Otherwise I'd try to replicate my users table and apply row filter rules. Would this be the correct way, or does anyone have suggestions?
r
rp_st
02/04/2023, 1:01 PMHey @tuyho
rp_st
02/04/2023, 1:02 PMThere isn’t a guide for that yet. But the easiest way would be to have two different cores, one per region
rp_st
02/04/2023, 1:02 PMAnd then two different backends that talk to each of the cores
rp_st
02/04/2023, 1:02 PMIf that’s not possible, then you can use the method you mentioned about row level filters.
rp_st
02/04/2023, 1:04 PMYou could also wait for when we have multi tenancy in which you could make the US users one tenant and EU users another tenant. This would allow you to store their data separately, whilst running one core and one backend for both the tenants
rp_st
02/04/2023, 1:04 PMThe multi tenancy feature should be out very soon
rp_st
02/04/2023, 1:04 PM1-2 months time
t
tuyho
02/04/2023, 2:45 PMThanks for the reply 👍 The multi tenancy feature would be exactly what I need right now 😄 How will you achieve this though? I am asking because I don't want to restructure my entire backend and database later on if I want to make use of the multi tenancy feature
r
rp_st
02/04/2023, 2:47 PMWell, first you will have to create two tenants in supertokens mapped to different databases.
rp_st
02/04/2023, 2:48 PMThen, you will need to tell supertokens about the tenant id of a user when they sign up. This can be determined based on which location they are in I guess
rp_st
02/04/2023, 2:48 PMAnd then supertokens will store that user’s info in the db mapped to that tenant
t
tuyho
02/04/2023, 2:52 PMThat makes sense! Btw about the user location, can I modify the default "emailpassword" users table to include a column with the location? Or should I use meta data for this? I think I remember that there was a guide to customize the default tables, but I can't find it anymore.
r
rp_st
02/04/2023, 2:52 PMYou shouldn’t modify our table structure
t
tuyho
02/04/2023, 2:53 PMGuess that would lead to problems with migrations
r
rp_st
02/04/2023, 2:57 PMWhy ?
t
tuyho
02/04/2023, 3:02 PMIf I change the table structure, and an update on supertokens core would try to modify the tables that could lead to migration issues, no? Or is there a different reason why I shouldn't modify the table structure?
r
rp_st
02/04/2023, 3:02 PMOh yea. That mainly.
t
tuyho
02/04/2023, 3:05 PMShould I use the user metadata feature to store user locations then? Or store it in a separate table?
r
rp_st
02/04/2023, 3:06 PMYou could store it in user metadata
rp_st
02/04/2023, 3:09 PMBut why would you want to store the location info anyway?
t
tuyho
02/04/2023, 3:27 PMWell my plan was to use it to apply a WHERE filter to assign them to the correct database. I guess I could just write them to the database directly. Is this what you meant?
r
rp_st
02/04/2023, 3:29 PMYea but you need to know the location before the user is created and based on that, store their data in one db vs another
rp_st
02/04/2023, 3:29 PMSo I’m not sure storing the location against the user I’d (which is after the user is created) will actually help
rp_st
02/04/2023, 3:29 PMEither way, multi tenancy isn’t out yet now anyway. So will talk again after it’s released 🙂
t
tuyho
02/04/2023, 3:30 PMAlright, thanks for your help! I really appreciate it