Important Notice - Forums is archived
To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.
Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
Scaleablilty upto 5000 users
Vaadin has no specific limitations and scalable well. The scalability will mostly depend on how you'll write your application and how you select the appropriate hardware for your load. Consider the following, vaadin-specific points while developing:
- Vaadin has a server side logic and your application and window (with all fields) instances are stored in the http session. So avoid having huge fields (arrays, lists) with some temporary data in those instances or at least mark them transient. Not doing so could produce extra server memory consumption
- Consider using or developeing Vaadin lazy ntainers for connecting data from your database or other sources to the UI elements. Remeber, that while client UI layer automatically handles server data lazy loading for you, at the server side you must handle lazy fetching from the database or so for yourself. You can also use already laze-fetch aware containers, such as HbnContainer, LuceneContainer and JPAContainer, which you can find in the directory.
From other points Vaadin performs well and does not produces any overhead, so except of memory consumption issues I mentioned above, Vaadin app is the same as any other web app, build using plain jsp/servlets.
As for me, our company successfully using Vaadin-based 24x7 app in one high-load project (Another high-load one will be launched soon) with approx up to 500-600 concurrent users and up to 8K unique users per day.