> Not to mention that session lookups becomes a single point of failure and can become a bottleneck for your application as you get more users. It's really diff

> Not to mention that session lookups becomes a single point of failure and can become a bottleneck for your application as you get more users. It's really difficult to scale well. You're going to run a Redis cluster just to manage sessions? Hello LATENCY!!! Welcome DDoS headache!!! Did anyone say backpressure issues??? How are you going to clean up stale sessions when a worker crashes? Good luck. I think this is pretty far-fetched hyperbole. How do you think websites managed logging in before JWTs existed roughly a decade ago? They used databases and in memory caches, which work fine up to a surprisingly large number of users.