Leveraging Spring Session helpers and configuration would benefit the project reducing the low-level code to maintain and backend implementations, but Vaadin's sessions are considerably heavier than typical common sessions so we must be careful on how (and how frequently) we serialize them.
Let's start by monitoring the demo application and benchmark performance with and without session serialization, simulating heavy sessions.
The size of the session fully depends on the amount of state (e.g. views) and business data that is stored in the application, ranging from 50kb to 1000kb per concurrent user, depending on the amount of business data that is stored in the session.
— excerpt fromhttps://vaadin.com/scalability
The second step would be to meter a full-blown application like Bakery.
heruan
commented
1 year ago
Leveraging Spring Session helpers and configuration would benefit the project reducing the low-level code to maintain and backend implementations, but Vaadin's sessions are considerably heavier than typical common sessions so we must be careful on how (and how frequently) we serialize them.
Let's start by monitoring the demo application and benchmark performance with and without session serialization, simulating heavy sessions.
The second step would be to meter a full-blown application like Bakery.