Even in a serverless environment it can be beneficial to still store your tokens in a db that your apps need to fetch from when run if you ever want your app to scale.
Yup, doing that for other areas of my ecosystem, it’s just much easier to use an App Token instead of pulling potentially thousands of access tokens from the DB and running the logic I mentioned against all of them
There’s a maximum number of 25 app access tokens, after which when you create more it’ll kill the first ones, so in a serverless app if there’s any concurrency it can’t scale beyond 25 instances, where as if for example you’re use AWS Lambda for your serverless apps, you can simply pull the token from a DynamoDB table which will have minimal delay and allow the serverless process to grow in concurrency/complexity.
I’m aware RE: there being a limit for App Access Tokens, I have a central authority to maintain a single one - and in my case, I store encrypted User Access Tokens in RDS (Since the user-facing side of the ecosystem requires it), so pulling them is not nearly as performant as I’d like (Referring to previous logic)