Answer the question
In order to leave comments, you need to log in
Which Java Web UI framework to choose?
Hello. Please advise a framework for creating a graphical web interface in java. It will be a web interface that will employ 10,000 people. At the same time, about a thousand will work in it. Something like a service desk. That is, all these 1000 people will be in continuous contact with the interface, and, consequently, with the server.
The framework should provide a more or less decent element design, because. I don't have time to draw all this economy myself. I'm looking at Vaadin or ZK, but there almost all actions with the interface generate a request to the server. Is it a burden for such frameworks? And what are the requirements for the server hosting the whole thing? How much more memory is needed compared to the same rails that will serve such traffic (not very large, but not small)?
Are there other similar frameworks?
I looked closely at GWT, but there I would have to tinker a lot with the design.
Thanks in advance.
Answer the question
In order to leave comments, you need to log in
GWT is one of the best options for such a task. If you have regular users, then the generated GWT script will be loaded into the browser once, and in the future the entire interface will be drawn in the browser, without calls to the server. Server calls will be needed only to receive / transmit pure data, without html / xml wrappers, and this will be done only when your logic really needs it, i.e., not every user action will cause a server call. In addition, frequently used data can be cached on the client, reducing traffic and load on the server. Another plus is that a lot of logic (for example, complex format-logical control) can be performed on the client, without calls to the server.
As for the design: GWT has a minimal set of components with which you can "draw" a dynamic interface of any complexity. If your goal is not to lure users to the site with beautiful / unusual ruffles, but to create a functional workplace, then the basic components should be enough.
By the way, the same Vaadin works on GWT. It complements it with its own components, but kills one of the main advantages of GWT - a high degree of independence from the server during user actions.
As for the load: 1000 people constantly working in the application is a lot. Prepare powerful servers for a DBMS and an application server, plus keep in mind the possibility of deploying a cluster to distribute the load.
If you are a Java programmer, then developing under GWT will be pleasant, or rather, as usual. For example, the process of developing under JSF is something else "fun", GWT is much better in this regard.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question