> Often we're talking about avoiding one db query per request in an application that is nowhere near any database-imposed bottlenecks. The reason you avoid the

> Often we're talking about avoiding one db query per request in an application that is nowhere near any database-imposed bottlenecks. The reason you avoid the db query isn't about trying to keep the db from being overloaded, it's that you can handle the request far away from the DB without needing to wait for the latency of hitting the DB. Which is also still a complete premature and unnecessary optimization for most people. And then someone realizes their use case requires revocation so they add a DB check anyways.