3 ms·
Forget this article. He just doesn't like everybody uses JWT instead of cookie in any case. I still think JWS is a good choice for REST API in stateless session
by llmfei 10y ago
Forget this article. He just doesn't like everybody uses JWT instead of cookie in any case. I still think JWS is a good choice for REST API in stateless session. I don't like to setup a redis server. What you need to do if the redis server cannot support so many users? So use JWT to keep stateless is a good choice.
- alfiepates 10y ago> He just doesn't like everybody uses JWT instead of cookie in any case. Why would anybody care about how you implement something in your application, unless they have a concrete reason that your implementation is less than ideal? > What you need to do if the redis server cannot support so many users? Scale up your infrastructure. You're need a LOT of users before this starts being an issue. > So use JWT to keep stateless is a good choice. The article explains why this is a bad idea... unless you can explain where the article is wrong? EDIT: Got caught in the middle of a thought, apologies.