What are the rules for Maven to divide modules according to business requirements?

I wonder if it"s good to do this.
I think generally module is divided into Controller service dao
for example, a device monitoring system based on Web
based on different types of devices (less than 10 expected) to build Module
each Module will write Controller service dao
this idea is to facilitate plugging and unplugging. If you add new equipment, you can just hit a jar package for the new device and dump it into the original project. Is it good to divide it in this way?

Apr.18,2022

if you have a question, divide it into modules by business, then how to handle the calls between modules

Menu