How to work with large multi-module applications on GWT

Question

We pay attention to proposals for a new architectural approach for our software.

We are currently working on a new interface for our ERP, and our sample at the time of launch was GWT + GWTP for the front-end.

Our first idea was to have a one-page application on which a compiled GWT application was created, where the functionality was modules aligned behind the main module.

Now we reach the critical phase of the process, when we actually create system functions. But we are facing a serious problem with this approach. At the moment, we have 41 GWT modules, which are compiled as dependencies of our main module with more than 3 GB of RAM and take 8-12 minutes. We expect that more than 400 modules will be installed at the end of the current development phase, and this will become unstable in terms of computing power to compile the application.

We have already covered some articles, such as Ben Northrop, at http://www.summa-tech.com/blog/2011/02/22/structuring-gwt-modules-for-large-applications . But we wanted other opinions on this issue.

Answer 1

We also use GWT, and we have more than 40 auxiliary modules and one main module. We currently support two browsers.

• To speed up development, we compile only one browser, which we use to debug the application. This saves us from compiling for other browsers during development.
• We also support internationalization, but during development we only collect English. This will save us some more compilation iterations. If there is a problem with the language or browser, then we will compile only that language or browser.
• One more thing - we collect and load only the necessary modules based on the module dependency.