You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Explain how a modular monolith can be structure with java and maven.
The current idea is to use maven modules to:
structure the overall application into business components. Each component becomes a separate maven module
structure each business component
The core as an own module
Each adapter an own module
To get the dependencies aligned use the dependency management of maven and create an application wide parent.pom to controll versions and used libraries
The article should be splitted into two parts:
Explain the modularization of one business component
Explain the modularization into business components.
In general give an overview of the benefits and concerns of this approach compared with a package structure.
The text was updated successfully, but these errors were encountered:
Removed the open comments.
Added the multiple monoltih question as a open issue in github devonfw#42.
Removed the records recommendation, as records cannot be inherited. That
might lead to problems with large and complex domain models.
Refs: devonfw#39
Explain how a modular monolith can be structure with java and maven.
The current idea is to use maven modules to:
To get the dependencies aligned use the dependency management of maven and create an application wide parent.pom to controll versions and used libraries
The article should be splitted into two parts:
In general give an overview of the benefits and concerns of this approach compared with a package structure.
The text was updated successfully, but these errors were encountered: