I love how easy it is to scale and add nodes to your cluster

thank you

Setup supertokens last night. Was super easy and really liking it so far.

Can i just say that the documentation is absolutely amazing

By far some of the best i have ever read. Theres so much documentation and its all so well written. Followed the emailpassword recipe for react

Quick question though, does super tokens scale well. Is it as simple as bringing up more docker containers?

thank you once again 🙂

Agreed 100%

> Quick question though, does super tokens scale well. Is it as simple as bringing up more docker containers? Yes. For several 10s of millions of users at least.. as much as one instance of mysql / postgres db can hold. In terms of requests per second, one core can handle 150 rps consistently. And you can add more nodes to increase this in a fairly linear fashion. You would need to configure the server thread pool size and db connection pool size accordingly though (these are configs available on the core)

I'm trying to update my boilerplate's supertokens to test things first how much code change is needed to move from v6.1 to v7 on

supertokens-node

and I noticed that you're aiming to be framework-agnostic which is awesome btw, should cater to a wider audience with this update 👌 On to my question, is there still a way to pass the error to the next middleware chain if I'm using express?

currently, I just pass the error to the

next()

of an express middleware

and it gets passed to my app's error middleware where everything there is centralized

I think you could just do

throw new UnauthenticatedError()

instead and it should reach your error middleware.

instead of doing

next(..)

, you should do

throw new ..

it should work, but if not, let us know.. might be a bug

trying to trace on your codebase how it's handling errors and hoping there's a

try...catch

that passes the error to express'

next()

xD

yea. it should be

oh i mean, even if there isn't a try / catch, then express should naturally call the first / next error handler anyway.

so it should reach your error handlers.

yea, I think that'd be true if the function passed isn't

async

if it's async and you await it, it would get called as well.

does it? let me check again 🤔 I remember having to wrap it as express just won't proceed to the next middleware last time I tested it so I had to wrap it with this

asyncHandler()

hmmm. I'll have to check too

iirc, this is one of the reasons why they made `koa`'s middlewares async by default as well as the coming v5 of express, since the current way of doing middlewares encourages callback hell

I see. So i think you are right..

So there might be an issue in the node SDK then. I'll release a fix for this very soon!

thanks for pointing this out.

but yea, I think it only becomes an issue on

async

functions, I'll verify my findings shortly

also, I think the signature of

verifySession

isn't right, at least from the Session recipe I'm using xD