Hello, I have a doubt regarding multiple instances on the supertokens core running at the same time? I'm looking at the self-hosted version, and was wondering if I have 3 docker containers running the supertokens core and pointing to the same DB does this create an issue or can I have as many containers running as I need. This is for a High Availability simulations on my side. The full use case is for example putting all my core instances behind a load balancer so I don't have a single point of failure.
r
rp_st
07/03/2022, 5:27 AM
Hey @mklovin1379
rp_st
07/03/2022, 5:28 AM
Each core is stateless and you can run as many as you like connected to the same db
rp_st
07/03/2022, 5:29 AM
You don't even need a load balance in frontend since our backend SDK queries them in a round robin. You just have to give the connection URI in the following format:
Copy code
core1address;core2address;core3address;
m
mklovin1379
07/03/2022, 5:32 AM
this means I could even have all cores behind a single DNS entry and provide that to the backend sdk, so that bringing up new container instances is transparent for my application?
r
rp_st
07/03/2022, 5:32 AM
yup. You can
rp_st
07/03/2022, 5:32 AM
Thats what we do for our managed service offering for scaled production users.
m
mklovin1379
07/03/2022, 5:34 AM
thanks! good to know that I'm heading in the right direction
SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).