Rename backend and simplify code structure
Problem to solve
In the constant quest of keeping the project structure as simple as possible in order to maintain and improve long term maintainability and decrease long term support cost, I suggest the following changes:
Give backend a more expressive name:
Since we are going to add further services in the foreseeable future I suggest to ditch the generic backend name in favour of something like management-service
Reduce the depth of the Kotlin code folder structure by getting rid of the folders com/mlreef/
:
This is especially easy to do since Kotlin supports omitting redundant folders. This means a file src/main/kotlin/Application.kt
can still have the package declaration package mlreef.com
Not especially important but the just ever so slight improvement.
Joining of mlreef-rest
and mlreef-domain
modules into one management-service
gradle project:
This one is a little bit more tricky. In my humble opinion, it will be a net benefit in terms of coding time and ease of understanding to remove the extra complexity of maintaining separate modules - albeit the complexity is small.
Additional Notes
Is this a cross-stage feature?
Links / references
/cc @si-ge-st