Design of a software architecture prototype for Modular Enterprise Resource Planning (ERP) in JAVA
Budget: €30 – €250 EUR
Technologies to use:
- JAVA EE (JDK 11 +/- 16)
- SPRING-BOOT
- SPRING SECURITY (or Keycloack)
- HIBERNATE
- MARIADB 10.5 (and POSTGRESQL) +/- oracle
- FLYWAY (7.7)
- VAADIN (14)
Description of the application:
1. The application will consist of several modules including a Core Module.
2. An installation of the application makes it possible to manage several companies (files). The data of each company is separated in different databases.
3. The activation of the modules in the application is done on the basis of a license key which activates the modules. The license also manages the number of users, the number of company files, and the duration of the license. Two avenues for this functionality:
• either all the modules are automatically loaded during installation
• Either the module is added as needed by a war (or jar) file: this is the preferred mode
4. User management will be done in the kernel module. Roles (profiles) allow users to limit access to modules, to the different pages (and functions) of each module.
- JAVA EE (JDK 11 +/- 16)
- SPRING-BOOT
- SPRING SECURITY (or Keycloack)
- HIBERNATE
- MARIADB 10.5 (and POSTGRESQL) +/- oracle
- FLYWAY (7.7)
- VAADIN (14)
Description of the application:
1. The application will consist of several modules including a Core Module.
2. An installation of the application makes it possible to manage several companies (files). The data of each company is separated in different databases.
3. The activation of the modules in the application is done on the basis of a license key which activates the modules. The license also manages the number of users, the number of company files, and the duration of the license. Two avenues for this functionality:
• either all the modules are automatically loaded during installation
• Either the module is added as needed by a war (or jar) file: this is the preferred mode
4. User management will be done in the kernel module. Roles (profiles) allow users to limit access to modules, to the different pages (and functions) of each module.