Vaadin Flow session memory keeps a low-traffic app on an oversized instance — is passivation viable?
A low-traffic Vaadin Flow application (assume Vaadin 24 on Spring Boot) costs more to host than its page-view count suggests. Because Flow holds each user's UI component tree in server memory tied to the HTTP session, instance sizing is driven by concurrent sessions and session timeout, not request volume. The goal is to move this workload to a smaller insta
vaadin