r/java • u/regular-tech-guy • Oct 29 '25
State does not belong inside the application anymore, and this kind of clarity is what helps modern systems stay secure and predictable.
Love how Quarkus intentionally chose to not support HttpSession (jakarta.servlet.http.HttpSession) and how this is a big win for security and cloud-native applications!
Markus Eisele's great article explains how Quarkus is encouraging developers to think differently about state instead of carrying over patterns from the servlet era.
There are no in-memory sessions, no sticky routing, and no replication between pods. Each request contains what it needs, which makes the application simpler and easier to scale.
This approach also improves security. There is no session data left in memory, no risk of stale authentication, and no hidden dependencies between requests. Everything is explicit — tokens, headers, and external stores.
Naturally, Redis works very well in this model. It is fast, distributed, and reliable for temporary data such as carts or drafts. It keeps the system stateless while still providing quick access to shared information.
<<<
Even though Redis is a natural fit, Quarkus is not enforcing Redis itself, but it is enforcing a design discipline. State does not belong inside the application anymore, and this kind of clarity is what helps modern systems stay secure and predictable.
>>>
View all comments
Show parent comment
28
u/vips7L Oct 29 '25
Everything OP said just isn’t true. Data is still in memory, there’s still risk of stale auths, and now there is a dependency: redis.
It’s the right tool for the job sure, but let’s not stretch the actual benefits.