ah, I found https://github.com/supertokens/superto...
# support-questions-legacy
m
ah, I found https://github.com/supertokens/supertokens-core/issues/529 So there is no JVM SDK. It sounds like we would need to add 2 processes to our app, the core microservice (jvm) + an api server (say, golang for least memory usage?)
n
Hi @mhuebert , Yep thats correct, SuperTokens core is designed to run as a standalone
And you would need an api server with our backend sdks integrated
(any would work, so thats a matter of preference)
m
are there examples of a "standalone" api server
n
Do you plan on using the same domain as your API layer for the standalone server? Or will it be on a separate domain
m
My first instinct is same domain
We want our whole app to be extremely easy to deploy on a single server
eg. put it on DigitalOcean and go
just a bit concerned about the ops burden if we have to add both a JVM supertokens process and API server process in addition to our JVM server
n
You could use our hosted solution to minimise the additional deployments on your end, that way we manage the core instance for you. For the backend side of things if youre on the same domain you just need to create a simple api server with the backend sdk integrated and it should work just fine. You will need to set the cookie domain to be
.youdomain.com
so that the cookies get sent to both your server and to the supertokens server (You can configure this when initialising supertokens)
9 Views