When I meant by cache (like maps and lettuce) is that at some point the database may reach a limit of connections or processing,
So instead of calling the db form something continuous like session handling, its better to use a cache system
Btw, jetty already uses a cache system called sessions in the request class.
By all means, don't. I use my framewrok with 100 hundred customers concurrently and I haven't hit a single issue on performance.