Hi,
I’ve tried jmix and it seems to be an awesome framework for developing enterprise applications. Good job!
One concern I have is related to the requirement of having sticky sessions as described in [1]. Does it mean that jmix application won’t behave well in the continuous deployment environment: every time application is redeployed, users will see a message that their session is expired and they have to refresh the page?
Thank you
Hi Nathan,
Yes, this is basically what it boils down to.
It is a inherit attribute of Vaadin Flow with its session state on the server.
That being said, there are ways to mitigate the problem. Vaadin has a so-called Kubernetes kit. With that they basically describe particular ways to support high availability requirements. See: Kubernetes Kit | Tools | Vaadin Docs
But from my understanding even with that a true stateless CD delivery model without any impact on users is not really possible.
But feel free to share your experience. I would be interested to learn about how other people deal with this situation.
Cheers
Mario