Details
-
Story
-
Resolution: Rejected
-
Major
-
None
-
None
-
None
Description
We have currently split the different bitrepository aspects into the following 5 modules:
- monitoring-service
- alarm-service
- integrity-service
- audit-trail-service
- webclient: Provides webGUI for the different services.
For all purposes we are currently deploy these to a single tomcat, so seen from an infrastructure perspective these are just one tomcat server.
The many modules have a number of more or less significant drawbacks: - More modules -> (may give) more complexity.
- Each module contains 95% the same libs, which comprise the vast majority of the war classes. This causes:
- The libs are duplicated across the war meaning 90% of the war content could be removed if the wars where merged.
- This duplication also means the lib classes are class loaded into the separate war classloadere, which means the permgen space is filled with duplicated loaded classes.
- 5 wars has to be deployed instead of just one.
An optimisation would then either be to merge the war modules into one war module or to change the service wars to be libs, which are aggregated into a war in the webclient module, which should then be renamed to something like service/server module.
Attachments
Issue Links
- related to
-
BITMAG-1006 Merge client modules into single module
- Resolved