> I'd assert for most businesses "for most businesses" you're never going to have enough traffic that a classic session database (even stored in, gasp, MySQL)

> I'd assert for most businesses "for most businesses" you're never going to have enough traffic that a classic session database (even stored in, gasp, MySQL) would be a bottleneck. JWT definitely has it's places but it has so much complexity, so many tradeoffs and footguns that it should only be used when you have a specific problem with a standard session system that you need to solve, not as the default.